[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v9] x86/altp2m: support for setting restrictions for an array of pages
- To: "Petre Ovidiu PIRCALABU" <ppircalabu@xxxxxxxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Wed, 13 Dec 2017 04:56:05 -0700
- Cc: "tim@xxxxxxx" <tim@xxxxxxx>, "sstabellini@xxxxxxxxxx" <sstabellini@xxxxxxxxxx>, "wei.liu2@xxxxxxxxxx" <wei.liu2@xxxxxxxxxx>, "rcojocaru@xxxxxxxxxxxxxxx" <rcojocaru@xxxxxxxxxxxxxxx>, "George.Dunlap@xxxxxxxxxxxxx" <George.Dunlap@xxxxxxxxxxxxx>, "andrew.cooper3@xxxxxxxxxx" <andrew.cooper3@xxxxxxxxxx>, "ian.jackson@xxxxxxxxxxxxx" <ian.jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, "tamas@xxxxxxxxxxxxx" <tamas@xxxxxxxxxxxxx>
- Delivery-date: Wed, 13 Dec 2017 11:56:14 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
>>> On 13.12.17 at 12:02, <ppircalabu@xxxxxxxxxxxxxxx> wrote:
> If we accept this case as valid, although highly unlikely, (opaque ==
> nr and not 0), calling p2m_set_mem_access_multi will do nothing except
> locking/unlocking p2m (case in which the performance penalty will be
> significantly greater).
That's exactly what I would expect to happen.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
