x86/emulate: Send vm_event from emulate
PATCH v12 1/1 x86/emulate: Send vm_event from emulate
A/D bit writes (on page walks) can be considered benign by an introspection agent, so receiving vm_events for them is a pessimization. We try here to optimize by filtering these events out.
Currently, we are fully emulating the instruction at RIP when the hardware sees an EPT fault with npfec.kind != npfec_kind_with_gla. This is, however, incorrect, because the instruction at RIP might legitimately cause an EPT fault of its own while accessing a _different_ page from the original one, where A/D were set.
The solution is to perform the whole emulation, while ignoring EPT restrictions for the walk part, and taking them into account for the "actual" emulating of the instruction at RIP. When we send out a vm_event, we don't want the emulation to complete, since in that case we won't be able to veto whatever it is doing. That would mean that we can't actually prevent any malicious activity, instead we'd only be able to report on it.
When we see a "send-vm_event" case while emulating, we need to first send the event out and then suspend the emulation (return X86EMUL_RETRY). After the emulation stops we'll call hvm_vm_event_do_resume() again after the introspection agent treats the event and resumes the guest. There, the instruction at RIP will be fully emulated (with the EPT ignored) if the introspection application allows it, and the guest will continue to run past the instruction.
A common example is if the hardware exits because of an EPT fault caused by a page walk, p2m_mem_access_check() decides if it is going to send a vm_event. If the vm_event was sent and it would be treated so it runs the instruction at RIP, that instruction might also hit a protected page and provoke a vm_event.
Now if npfec.kind == npfec_kind_in_gpt and d->arch.monitor.inguest_pagefault_disabled is true then we are in the page walk case and we can do this emulation optimization and emulate the page walk while ignoring the EPT, but don't ignore the EPT for the emulation of the actual instruction.
In the first case we would have 2 EPT events, in the second case we would have 1 EPT event if the instruction at the RIP triggers an EPT event.
We use hvmemul_map_linear_addr() to intercept write access and __hvm_copy() to intercept exec, read and write access.
In order to have __hvm_copy() issue ~X86EMUL_RETRY a new return type, HVMTRANS_need_retry, was added and all the places that consume HVMTRANS* and needed adjustment where changed accordingly.
hvm_emulate_send_vm_event() can return false if there was no violation, if there was an error from monitor_traps() or p2m_get_mem_access(). -ESRCH from p2m_get_mem_access() is treated as restricted access.
NOTE: hvm_emulate_send_vm_event() assumes the caller will enable/disable arch.vm_event->send_event
---
Changes since V11:
- Rename HVMTRANS_bad_gfn_access to HVMTRANS_need_retry
- Check unlikely(v->arch.vm_event) first
- Move send_event disable from hvm_monitor_check_p2m() to the
caller
- Add the missing HVMTRANS_need_retry checks for HVMTRANS*
consumers.
--- xen/arch/x86/hvm/emulate.c | 18 ++++++- xen/arch/x86/hvm/hvm.c | 9 ++++ xen/arch/x86/hvm/intercept.c | 2 + xen/arch/x86/hvm/monitor.c | 78 +++++++++++++++++++++++++++++++ xen/arch/x86/mm/mem_access.c | 9 +++- xen/arch/x86/mm/shadow/hvm.c | 1 + xen/include/asm-x86/hvm/monitor.h | 3 ++ xen/include/asm-x86/hvm/support.h | 1 + xen/include/asm-x86/vm_event.h | 2 + 9 files changed, 121 insertions(+), 2 deletions(-)
xen/arch/x86/hvm/emulate.c +17 -1
@@ -548,6 +548,7 @@ static void *hvmemul_map_linear_addr(unsigned int nr_frames = ((linear + bytes - !!bytes) >>PAGE_SHIFT ) - (linear >>PAGE_SHIFT ) +1 ;unsigned int i; +gfn_t gfn;/* * mfn points to the next free slot. All used slots have a page reference
@@ -582,7 +583,7 @@ static void *hvmemul_map_linear_addr(ASSERT (mfn_x (*mfn) ==0 ); res =hvm_translate_get_page (curr, addr, true, pfec, - &pfinfo, &page,NULL , &p2mt); + &pfinfo, &page, &gfn, &p2mt);switch ( res ) {
@@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry: err =ERR_PTR (~X86EMUL_RETRY ); goto out;
@@ -626,6 +628,14 @@ static void *hvmemul_map_linear_addr(ASSERT (p2mt == p2m_ram_logdirty || !p2m_is_readonly (p2mt)); } + +if (unlikely (curr->arch.vm_event) && + curr->arch.vm_event->send_event && +hvm_monitor_check_p2m (addr, gfn, pfec, npfec_kind_with_gla) ) + { + err =ERR_PTR (~X86EMUL_RETRY ); + goto out; + } }/* Entire access within a single frame? */
@@ -1141,6 +1151,7 @@ static int linear_read(unsigned long addr, unsigned int bytes, void *p_data,case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:return X86EMUL_RETRY ; }
@@ -1192,6 +1203,7 @@ static int linear_write(unsigned long addr, unsigned int bytes, void *p_data,case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:return X86EMUL_RETRY ; }
@@ -1852,6 +1864,8 @@ static int hvmemul_rep_movs(xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +if ( rc == HVMTRANS_gfn_paged_out )return X86EMUL_RETRY ;if ( rc == HVMTRANS_gfn_shared )
@@ -1964,6 +1978,8 @@ static int hvmemul_rep_stos(if ( buf != p_data )xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +switch ( rc ) {case HVMTRANS_gfn_paged_out:
xen/arch/x86/hvm/hvm.c +9 -0
@@ -3236,6 +3236,15 @@ static enum hvm_translation_result __hvm_copy(return HVMTRANS_bad_gfn_to_mfn; } +if (unlikely (v->arch.vm_event) && + (flags & HVMCOPY_linear) && + v->arch.vm_event->send_event && +hvm_monitor_check_p2m (addr, gfn, pfec, npfec_kind_with_gla) ) + { +put_page (page); +return HVMTRANS_need_retry; + } + p = (char *)__map_domain_page (page) + (addr & ~PAGE_MASK );if ( flags & HVMCOPY_to_guest )
xen/arch/x86/hvm/intercept.c +2 -0
@@ -145,6 +145,7 @@ int hvm_process_io_intercept(const struct hvm_io_handler *handler,case HVMTRANS_bad_linear_to_gfn:case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:ASSERT_UNREACHABLE ();/* fall through */ default :
@@ -174,6 +175,7 @@ int hvm_process_io_intercept(const struct hvm_io_handler *handler,case HVMTRANS_bad_linear_to_gfn:case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:ASSERT_UNREACHABLE ();/* fall through */ default :
xen/arch/x86/hvm/monitor.c +78 -0
92 lines not on this page · raw message
xen/arch/x86/mm/mem_access.c +8 -1
@@ -210,11 +210,18 @@ bool p2m_mem_access_check(paddr_t gpa, unsigned long gla,return true; } } + +/* +* Try to avoid sending a mem event. Suppress events caused by page-walks +* by emulating but still checking mem_access violations. +*/ if (vm_event_check_ring (d->vm_event_monitor) && d->arch.monitor.inguest_pagefault_disabled && - npfec.kind != npfec_kind_with_gla )/* don't send a mem_event */ + npfec.kind == npfec_kind_in_gpt ) { + v->arch.vm_event->send_event = true;hvm_emulate_one_vm_event (EMUL_KIND_NORMAL , TRAP_invalid_op,X86_EVENT_NO_EC ); + v->arch.vm_event->send_event = false;return true; }
xen/arch/x86/mm/shadow/hvm.c +1 -0
@@ -139,6 +139,7 @@ hvm_read(enum x86_segment seg,return X86EMUL_UNHANDLEABLE ;case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:return X86EMUL_RETRY ; }
xen/include/asm-x86/hvm/monitor.h +3 -0
@@ -49,6 +49,9 @@ void hvm_monitor_interrupt(unsigned int vector, unsigned int type, unsigned int err, uint64_t cr2);bool hvm_monitor_emul_unimplemented (void ); +bool hvm_monitor_check_p2m (unsigned long gla,gfn_t gfn,uint32_t pfec, +uint16_t kind); +#endif /* __ASM_X86_HVM_MONITOR_H__ */ /*
xen/include/asm-x86/hvm/support.h +1 -0
@@ -61,6 +61,7 @@ enum hvm_translation_result { HVMTRANS_unhandleable, HVMTRANS_gfn_paged_out, HVMTRANS_gfn_shared, + HVMTRANS_need_retry, };/*
xen/include/asm-x86/vm_event.h +2 -0
@@ -36,6 +36,8 @@ struct arch_vm_event {bool set_gprs;/* A sync vm_event has been sent and we're not done handling it. */ bool sync_event; +/* Send mem access events from emulator */ +bool send_event; };int vm_event_init_domain (struct domain *d);
Signature · 7 lines
2.17.1 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 3 lines · Alexandru Stefan ISAILA
In order to have
__hvm_copy()issue ~X86EMUL_RETRY a new return type,HVMTRANS_need_retry, was added and all the places that consume HVMTRANS* and needed adjustment where changed accordingly.
This is wrong and hence confusing: __hvm_copy() would never return ~X86EMUL_RETRY. In fact I think you've confused yourself enough to make a questionable (possibly resulting) change:
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 586
Quoted 6 lines
xen/arch/x86/hvm/emulate.c +1
-1@@ -582,7 +583,7 @@ static void *hvmemul_map_linear_addr(ASSERT (mfn_x (*mfn) ==0 ); res =hvm_translate_get_page (curr, addr, true, pfec, - &pfinfo, &page,NULL , &p2mt); + &pfinfo, &page, &gfn, &p2mt);
This function ...
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 605
Quoted 7 lines
xen/arch/x86/hvm/emulate.c +1
-0switch ( res ) {@@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:
... can't return this value, so you should omit this addition, letting the new return value go through "default:".
Quoted 10 lines
xen/arch/x86/hvm/emulate.c +2
-0@@ -1852,6 +1864,8 @@ static int hvmemul_rep_movs(xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +if ( rc == HVMTRANS_gfn_paged_out )return X86EMUL_RETRY ;if ( rc == HVMTRANS_gfn_shared )
xen/arch/x86/hvm/emulate.c static int hvmemul_rep_stos( · line 1985
Quoted 8 lines
xen/arch/x86/hvm/emulate.c +2
-0@@ -1964,6 +1978,8 @@ static int hvmemul_rep_stos(if ( buf != p_data )xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +switch ( rc ) {case HVMTRANS_gfn_paged_out:
Looking at this again, I think it would better be an addition to the switch() (using ASSERT_UNREACHABLE()). Generally this is true for the rep_movs case as well, but that one would first need converting to switch(), which I agree is beyond the scope of this change. In both cases a brief comment would seem worthwhile adding, clarifying that the new return value can result from hvm_copy_*_guest_linear() only. This might become relevant in particular if, down the road, we invent more cases where HVMTRANS_need_retry is produced.
Then again maybe switching rep_movs to switch() would still be a good thing to do here: Don't you agree that from an abstract pov in both cases above X86EMUL_RETRY should be produced, if at a future point physical accesses could also produce HVMTRANS_need_retry? With this retaining the assertions is certainly an option, but I think the fallback return value for this case should still be X86EMUL_RETRY.
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 8 lines · Jan Beulich
Quoted 3 lines · Alexandru Stefan ISAILA
In order to have
__hvm_copy()issue ~X86EMUL_RETRY a new return type,HVMTRANS_need_retry, was added and all the places that consume HVMTRANS* and needed adjustment where changed accordingly.This is wrong and hence confusing:
__hvm_copy()would never return ~X86EMUL_RETRY. In fact I think you've confused yourself enough to make a questionable (possibly resulting) change:
The idea was to get X86EMUL_RETRY down the line from __hvm_copy(). I will adjust this.
Quoted 14 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 586
Quoted 7 lines
xen/arch/x86/hvm/emulate.c +1
-1@@ -582,7 +583,7 @@ static void *hvmemul_map_linear_addr(ASSERT (mfn_x (*mfn) ==0 ); res =hvm_translate_get_page (curr, addr, true, pfec, - &pfinfo, &page,NULL , &p2mt); + &pfinfo, &page, &gfn, &p2mt);This function ...
Quoted 4 lines
xen/arch/x86/hvm/emulate.c +0
-0switch ( res ) {@@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(
Quoted 6 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 605
Quoted 3 lines
xen/arch/x86/hvm/emulate.c +1
-0case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:... can't return this value, so you should omit this addition, letting the new return value go through "default:".
It is very clear that HVMTRANS_need_retry will not be returned form that function. At least for now. I thought you wanted to have every possible case covered in the switch. I can remove that case, there is not problem here because, like I've said, it will never enter that case.
But as you said later work with HVMTRANS_need_retry will result in returning X86EMUL_RETRY. Any way it's your call if I should remove it or not.
Quoted 14 lines
Quoted 14 lines
xen/arch/x86/hvm/emulate.c +2
-0@@ -1852,6 +1864,8 @@ static int hvmemul_rep_movs(xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +if ( rc == HVMTRANS_gfn_paged_out )return X86EMUL_RETRY ;if ( rc == HVMTRANS_gfn_shared )@@ -1964,6 +1978,8 @@ static int hvmemul_rep_stos(if ( buf != p_data )xfree (buf);
Quoted 10 lines
xen/arch/x86/hvm/emulate.c static int hvmemul_rep_stos( · line 1985
Quoted 5 lines
xen/arch/x86/hvm/emulate.c +2
-0+ASSERT (rc != HVMTRANS_need_retry); +switch ( rc ) {case HVMTRANS_gfn_paged_out:Looking at this again, I think it would better be an addition to the
switch()(usingASSERT_UNREACHABLE()). Generally this is true for therep_movscase as well, but that one would first need converting toswitch(), which I agree is beyond the scope
I agree that this is beyond the scope of this patch but it's not that big of a change and it can be done.
But isn't having a default ASSERT_UNREACHABLE(); in both switch cases change the behavior of the function?
Quoted 5 lines
of this change. In both cases a brief comment would seem worthwhile adding, clarifying that the new return value can result from hvm_copy_*_guest_linear() only. This might become relevant in particular if, down the road, we invent more cases where
HVMTRANS_need_retryis produced.
Is this comment aimed for the commit message or another place?
Quoted 9 lines
Then again maybe switching
rep_movstoswitch()would still be a good thing to do here: Don't you agree that from an abstract pov in both cases aboveX86EMUL_RETRYshould be produced, if at a future point physical accesses could also produceHVMTRANS_need_retry? With this retaining the assertions is certainly an option, but I think the fallback return value for this case should still beX86EMUL_RETRY.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 36 lines · Alexandru Stefan ISAILA
Quoted 8 lines · Jan Beulich
Quoted 3 lines · Alexandru Stefan ISAILA
In order to have
__hvm_copy()issue ~X86EMUL_RETRY a new return type,HVMTRANS_need_retry, was added and all the places that consume HVMTRANS* and needed adjustment where changed accordingly.This is wrong and hence confusing:
__hvm_copy()would never return ~X86EMUL_RETRY. In fact I think you've confused yourself enough to make a questionable (possibly resulting) change:The idea was to get
X86EMUL_RETRYdown the line from__hvm_copy(). I will adjust this.Quoted 14 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 586
Quoted 7 lines
xen/arch/x86/hvm/emulate.c +1
-1@@ -582,7 +583,7 @@ static void *hvmemul_map_linear_addr(ASSERT (mfn_x (*mfn) ==0 ); res =hvm_translate_get_page (curr, addr, true, pfec, - &pfinfo, &page,NULL , &p2mt); + &pfinfo, &page, &gfn, &p2mt);This function ...
Quoted 4 lines
xen/arch/x86/hvm/emulate.c +0
-0switch ( res ) {@@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(Quoted 6 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 605
Quoted 3 lines
xen/arch/x86/hvm/emulate.c +1
-0case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:... can't return this value, so you should omit this addition, letting the new return value go through "default:".
Quoted 8 lines
It is very clear that
HVMTRANS_need_retrywill not be returned form that function. At least for now. I thought you wanted to have every possible case covered in the switch. I can remove that case, there is not problem here because, like I've said, it will never enter that case.But as you said later work with
HVMTRANS_need_retrywill result in returningX86EMUL_RETRY. Any way it's your call if I should remove it or not.
The result should be consistent (i.e. between the case here and the rep_movs / rep_stos cases below). Overall I think it would be cleanest if in all three cases an ASSERT_UNREACHABLE() fell through to a "return X86EMUL_RETRY;".
Quoted 24 lines
Quoted 13 lines
Quoted 13 lines
xen/arch/x86/hvm/emulate.c +2
-0@@ -1852,6 +1864,8 @@ static int hvmemul_rep_movs(xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +if ( rc == HVMTRANS_gfn_paged_out )return X86EMUL_RETRY ;if ( rc == HVMTRANS_gfn_shared )@@ -1964,6 +1978,8 @@ static int hvmemul_rep_stos(if ( buf != p_data )xfree (buf);Quoted 10 lines
xen/arch/x86/hvm/emulate.c static int hvmemul_rep_stos( · line 1985
Quoted 5 lines
xen/arch/x86/hvm/emulate.c +2
-0+ASSERT (rc != HVMTRANS_need_retry); +switch ( rc ) {case HVMTRANS_gfn_paged_out:Looking at this again, I think it would better be an addition to the
switch()(usingASSERT_UNREACHABLE()). Generally this is true for therep_movscase as well, but that one would first need converting toswitch(), which I agree is beyond the scope
Quoted 5 lines
I agree that this is beyond the scope of this patch but it's not that big of a change and it can be done.
But isn't having a default
ASSERT_UNREACHABLE(); in both switch cases change the behavior of the function?
It shouldn't be the default case that gains this assertion, but the HVMTRANS_need_retry one that is to be added.
Quoted 7 lines
Quoted 5 lines
of this change. In both cases a brief comment would seem worthwhile adding, clarifying that the new return value can result from hvm_copy_*_guest_linear() only. This might become relevant in particular if, down the road, we invent more cases where
HVMTRANS_need_retryis produced.Is this comment aimed for the commit message or another place?
If you go the ASSERT_UNREACHABLE() route, then the comment(s) should be code comments next to these assertions. They'd be there to avoid people having to dig out the reason for why they're there, to make it easy to decide whether it is safe to drop them once some new producer of HVMTRANS_need_retry would appear.
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 9 lines · Jan Beulich
Quoted 8 lines · Alexandru Stefan ISAILA
Quoted 5 lines · Jan Beulich
Quoted 3 lines · Alexandru Stefan ISAILA
In order to have
__hvm_copy()issue ~X86EMUL_RETRY a new return type,HVMTRANS_need_retry, was added and all the places that consume HVMTRANS* and needed adjustment where changed accordingly.
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines
This is wrong and hence confusing:
__hvm_copy()would never return ~X86EMUL_RETRY. In fact I think you've confused yourself enough to make a questionable (possibly resulting) change:The idea was to get
X86EMUL_RETRYdown the line from__hvm_copy(). I will adjust this.
This will be changed for:
"A new return type was added, HVMTRANS_need_retry, in order to have all the places that consume HVMTRANS* return X86EMUL_RETRY."
Quoted 27 lines
Quoted 27 lines
Quoted 15 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 586
Quoted 8 lines
xen/arch/x86/hvm/emulate.c +1
-1@@ -582,7 +583,7 @@ static void *hvmemul_map_linear_addr(ASSERT (mfn_x (*mfn) ==0 ); res =hvm_translate_get_page (curr, addr, true, pfec, - &pfinfo, &page,NULL , &p2mt); + &pfinfo, &page, &gfn, &p2mt);This function ...
Quoted 4 lines
xen/arch/x86/hvm/emulate.c +0
-0switch ( res ) {@@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(Quoted 6 lines
xen/arch/x86/hvm/emulate.c static void *hvmemul_map_linear_addr( · line 605
Quoted 3 lines
xen/arch/x86/hvm/emulate.c +1
-0case HVMTRANS_gfn_paged_out:case HVMTRANS_gfn_shared: +case HVMTRANS_need_retry:... can't return this value, so you should omit this addition, letting the new return value go through "default:".
It is very clear that
HVMTRANS_need_retrywill not be returned form that function. At least for now. I thought you wanted to have every possible case covered in the switch. I can remove that case, there is not problem here because, like I've said, it will never enter that case.
Quoted 9 lines
Quoted 3 lines
But as you said later work with
HVMTRANS_need_retrywill result in returningX86EMUL_RETRY. Any way it's your call if I should remove it or not.The result should be consistent (i.e. between the case here and the
rep_movs/rep_stoscases below). Overall I think it would be cleanest if in all three cases anASSERT_UNREACHABLE()fell through to a "returnX86EMUL_RETRY;".
Ok, just to make sure this is what is needed and limit the patch versions, rep_movs / rep_stos should have a switch like this:
switch ( rc )
{
case HVMTRANS_okay:
return X86EMUL_OKAY;
case HVMTRANS_need_retry:
ASSERT_UNREACHABLE();
/* fall through */
case HVMTRANS_gfn_paged_out:
case HVMTRANS_gfn_shared:
return X86EMUL_RETRY;
}Then hvmemul_map_linear_addr() should have:
case HVMTRANS_need_retry:
ASSERT_UNREACHABLE();
/* fall through */
case HVMTRANS_gfn_shared:
case HVMTRANS_gfn_paged_out:
err = ERR_PTR(~X86EMUL_RETRY);Quoted 39 lines
Quoted 24 lines
Quoted 13 lines
Quoted 13 lines
xen/arch/x86/hvm/emulate.c +2
-0@@ -1852,6 +1864,8 @@ static int hvmemul_rep_movs(xfree (buf); +ASSERT (rc != HVMTRANS_need_retry); +if ( rc == HVMTRANS_gfn_paged_out )return X86EMUL_RETRY ;if ( rc == HVMTRANS_gfn_shared )@@ -1964,6 +1978,8 @@ static int hvmemul_rep_stos(if ( buf != p_data )xfree (buf);Quoted 10 lines
xen/arch/x86/hvm/emulate.c static int hvmemul_rep_stos( · line 1985
Quoted 5 lines
xen/arch/x86/hvm/emulate.c +2
-0+ASSERT (rc != HVMTRANS_need_retry); +switch ( rc ) {case HVMTRANS_gfn_paged_out:Looking at this again, I think it would better be an addition to the
switch()(usingASSERT_UNREACHABLE()). Generally this is true for therep_movscase as well, but that one would first need converting toswitch(), which I agree is beyond the scopeQuoted 5 lines
I agree that this is beyond the scope of this patch but it's not that big of a change and it can be done.
But isn't having a default
ASSERT_UNREACHABLE(); in both switch cases change the behavior of the function?It shouldn't be the default case that gains this assertion, but the
HVMTRANS_need_retryone that is to be added.Quoted 6 lines
Quoted 5 lines
of this change. In both cases a brief comment would seem worthwhile adding, clarifying that the new return value can result from hvm_copy_*_guest_linear() only. This might become relevant in particular if, down the road, we invent more cases where
HVMTRANS_need_retryis produced.
Quoted 9 lines
Quoted 1 line
Is this comment aimed for the commit message or another place?
If you go the
ASSERT_UNREACHABLE()route, then the comment(s) should be code comments next to these assertions. They'd be there to avoid people having to dig out the reason for why they're there, to make it easy to decide whether it is safe to drop them once some new producer ofHVMTRANS_need_retrywould appear.
Alex
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 15 lines · Alexandru Stefan ISAILA
Ok, just to make sure this is what is needed and limit the patch versions,
rep_movs/rep_stosshould have a switch like this:switch ( rc ) { case HVMTRANS_okay: return X86EMUL_OKAY; case HVMTRANS_need_retry: ASSERT_UNREACHABLE(); /* fall through */ case HVMTRANS_gfn_paged_out: case HVMTRANS_gfn_shared: return X86EMUL_RETRY; }
Quoted 9 lines
Then
hvmemul_map_linear_addr()should have:case HVMTRANS_need_retry: ASSERT_UNREACHABLE(); /* fall through */ case HVMTRANS_gfn_shared: case HVMTRANS_gfn_paged_out: err = ERR_PTR(~X86EMUL_RETRY);
Right, plus a brief comment on the assertions as to why they're there (to clarify under what condition it would be fine to drop them).
Jan
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel