From: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/2] memory: don't hand MFN info to translated guests
Date: Mon, 19 Jun 2017 08:48:25 -0600 [thread overview]
Message-ID: <CABfawhnPZ5octUMx1rOvu2aCjaiCwOkHR-mdxJbkyATcZ6mpKA@mail.gmail.com> (raw)
In-Reply-To: <ca52d3a2-8208-2eb3-d362-a09a052e4660@citrix.com>
On Mon, Jun 19, 2017 at 3:11 AM, George Dunlap <george.dunlap@citrix.com> wrote:
> On 19/06/17 09:15, Jan Beulich wrote:
>>>>> On 18.06.17 at 21:19, <tamas.k.lengyel@gmail.com> wrote:
>>> On Tue, Apr 4, 2017 at 1:04 PM, Andrew Cooper <andrew.cooper3@citrix.com>
>>> wrote:
>>>> On 04/04/17 14:14, Jan Beulich wrote:
>>>>> We shouldn't hand MFN info back from increase-reservation for
>>>>> translated domains, just like we don't for populate-physmap and
>>>>> memory-exchange. For full symmetry also check for a NULL guest handle
>>>>> in populate_physmap() (but note this makes no sense in
>>>>> memory_exchange(), as there the array is also an input).
>>>>>
>>>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>>>
>>>> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>>
>>> Unfortunately I just had time to do testing with this change and I
>>> have to report that introduces a critical regression for my tools.
>>> With this change in-place performing increase_reservation on a target
>>> domain no longer reports the guest frame number for external tools,
>>> thus completely breaking advanced use-cases that require this
>>> information to be able to do altp2m gfn remapping. This is a critical
>>> step in being able to introduce shadow-pages that are used to hide
>>> breakpoints and other memory modifications from the guest.
>>
>> While I can see your point, I'm afraid that's not how the
>> interface was meant to be used.
>
> Well the first question to ask is, is that hypercall part of the stable
> interface? If so, then the standard should be, "Don't break people who
> call it unless there is really no other way around it." Sure, it was a
> mistake whoever introduced that, but if Tamas is building on a "stable"
> interface he should be able to rely on that interface being maintained,
> at least until we can find a suitable replacement.
>
> -George
>
Of course if a suitable replacement can be made that gets me the
information I need that would work too. At the moment I'm not aware of
any other hypercall I could use for this purpose.
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-19 14:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 12:53 [PATCH 0/2] memory: XSA-212 follow-up Jan Beulich
2017-04-04 13:13 ` [PATCH 1/2] memory: exit early from memory_exchange() upon write-back error Jan Beulich
2017-04-04 18:45 ` Andrew Cooper
2017-04-05 6:58 ` Jan Beulich
2017-04-05 7:00 ` Jan Beulich
2017-04-04 13:14 ` [PATCH 2/2] memory: don't hand MFN info to translated guests Jan Beulich
2017-04-04 19:04 ` Andrew Cooper
2017-06-18 19:19 ` Tamas K Lengyel
2017-06-19 8:15 ` Jan Beulich
2017-06-19 9:09 ` Julien Grall
2017-06-19 14:39 ` Tamas K Lengyel
2017-06-19 14:52 ` Julien Grall
2017-06-19 14:57 ` Tamas K Lengyel
2017-06-19 15:34 ` Julien Grall
2017-06-19 16:38 ` Tamas K Lengyel
2017-06-19 16:57 ` Tamas K Lengyel
2017-06-19 9:11 ` George Dunlap
2017-06-19 10:52 ` Jan Beulich
2017-06-19 14:48 ` Tamas K Lengyel [this message]
2017-06-19 14:54 ` George Dunlap
2017-06-19 14:56 ` Tamas K Lengyel
2017-04-05 13:12 ` [PATCH 0/2] memory: XSA-212 follow-up Julien Grall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABfawhnPZ5octUMx1rOvu2aCjaiCwOkHR-mdxJbkyATcZ6mpKA@mail.gmail.com \
--to=tamas.k.lengyel@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).