On 20/03/15 16:27, Jan Beulich wrote:
> Again because Xen doesn't get to see all guest writes, it shouldn't
> serve reads from its cache before having seen a write to the respective
> address.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
>>> On 23.03.15 at 20:11, wrote:
> On Fri, Mar 20, 2015 at 04:27:57PM +, Jan Beulich wrote:
>> Again because Xen doesn't get to see all guest writes, it shouldn't
>> serve reads from its cache before having seen a write to the respective
>> address.
>>
>> Signed-off-by: Jan Beulich
>
> Revi
On Fri, Mar 20, 2015 at 04:27:57PM +, Jan Beulich wrote:
> Again because Xen doesn't get to see all guest writes, it shouldn't
> serve reads from its cache before having seen a write to the respective
> address.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Konrad Rzeszutek Wilk
>
> --- a/x
Again because Xen doesn't get to see all guest writes, it shouldn't
serve reads from its cache before having seen a write to the respective
address.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/hvm/vmsi.c
+++ b/xen/arch/x86/hvm/vmsi.c
@@ -153,12 +153,15 @@ struct msixtbl_entry
/* TODO: res