From: Julien Grall <julien.grall@arm.com>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
Jason Andryuk <jandryuk@gmail.com>, Wei Liu <wei.liu2@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/domain: Drop the only-written smap_check_policy infrastructure
Date: Tue, 8 May 2018 17:26:41 +0100 [thread overview]
Message-ID: <9842f7ca-d82f-16e8-b01c-2d16e4bec720@arm.com> (raw)
In-Reply-To: <dc096ec0-3880-7965-7d45-8c7caea29113@citrix.com>
Hi,
On 08/05/18 17:20, Andrew Cooper wrote:
> On 08/05/18 17:10, Roger Pau Monné wrote:
>> On Tue, May 08, 2018 at 02:03:04PM +0100, Andrew Cooper wrote:
>>> c/s 4c5d78a10d "x86/pagewalk: Re-implement the pagetable walker" dropped the
>>> consumer of smap_policy. Looking at c/s 31ae587e6f which introduced the
>>> smap_check logic, it exists only to work around a bug in guest_walk_tables()
>>> was resolved by the aformentioned commit.
>>>
>>> Remove the unused variables and associated infrastructure.
>>>
>>> Reported-by: Jason Andryuk <jandryuk@gmail.com>
>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>>
>>> diff --git a/xen/include/asm-x86/domain.h b/xen/include/asm-x86/domain.h
>>> index 8b66096..197f8d6 100644
>>> --- a/xen/include/asm-x86/domain.h
>>> +++ b/xen/include/asm-x86/domain.h
>>> @@ -595,7 +583,6 @@ struct arch_vcpu
>>>
>>> struct guest_memory_policy
>>> {
>>> - smap_check_policy_t smap_policy;
>>> bool nested_guest_mode;
>> Maybe guest_memory_policy could be dropped and
>> update_guest_memory_policy updated to take a bool nested_mode
>> parameter?
>
> update_guest_memory_policy() stores the old value in the passed
> structure, and would more accurately be toggle_guest_memory_policy()
> when it came to guest mode.
>
>> Or the function can be dropped altogether likely.
>
> Sadly not yet. This exists because of Xen's virtual-address based API
> for the shared info and time mappings. This API is bad and wrong and
> wants fixing. ISTR Juergen and Julien having plans to deal with this?
This should indeed be fixed properly, I was waiting some answer on my
questions before attempting to go further on a fix (see [1] and [2]). I
didn't have bandwidth so far to ping on the subject.
Cheers,
[1]
https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg08836.html
[2]
https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg08835.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-05-08 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 13:03 [PATCH] x86/domain: Drop the only-written smap_check_policy infrastructure Andrew Cooper
2018-05-08 16:05 ` George Dunlap
2018-05-08 16:08 ` Juergen Gross
2018-05-08 16:13 ` Andrew Cooper
2018-05-08 16:10 ` Roger Pau Monné
2018-05-08 16:20 ` Andrew Cooper
2018-05-08 16:26 ` Julien Grall [this message]
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=9842f7ca-d82f-16e8-b01c-2d16e4bec720@arm.com \
--to=julien.grall@arm.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).