[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [for-4.7] x86/emulate: synchronize LOCKed instruction emulation
- To: Jan Beulich <jbeulich@xxxxxxxx>, <rcojocaru@xxxxxxxxxxxxxxx>
- From: George Dunlap <george.dunlap@xxxxxxxxxx>
- Date: Tue, 26 Apr 2016 17:03:46 +0100
- Cc: tim@xxxxxxx, wei.liu2@xxxxxxxxxx, george.dunlap@xxxxxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, paul.durrant@xxxxxxxxxx, david.vrabel@xxxxxxxxxx, keir@xxxxxxx
- Delivery-date: Tue, 26 Apr 2016 16:04:02 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 19/04/16 17:35, Jan Beulich wrote:
>>>> Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> 04/19/16 1:01 PM >>>
>> I think this might be because the LOCK prefix should guarantee that the
>> instruction that follows it has exclusive use of shared memory (for both
>> reads and writes) but I might be misreading the docs:
>
> LOCK definitely has no effect on other than the instruction it gets applied
> to.
Sorry I wasn't involved in this discussion -- what was the conclusion here?
FWIW Andy's suggestion of using a stub seemed like the most robust
solution, if that could be made to work.
If you're going to submit a patch substantially similar to this one, let
me know so I can review the mm bits of the original patch.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
