From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Tim Deegan <tim@xen.org>, Wei Liu <wl@xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86/shadow: Reposition sh_remove_write_access_from_sl1p()
Date: Thu, 21 May 2020 14:22:52 +0200 [thread overview]
Message-ID: <20200521111441.GS54375@Air-de-Roger> (raw)
In-Reply-To: <91c7f537-1d0e-4a9d-16a8-c02fa30d2d80@citrix.com>
On Thu, May 21, 2020 at 11:32:04AM +0100, Andrew Cooper wrote:
> On 21/05/2020 11:26, Roger Pau Monné wrote:
> > On Thu, May 21, 2020 at 10:04:28AM +0100, Andrew Cooper wrote:
> >> +static int sh_remove_write_access_from_sl1p(struct domain *d, mfn_t gmfn,
> >> + mfn_t smfn, unsigned long off)
> >> +{
> >> + struct page_info *sp = mfn_to_page(smfn);
> >> +
> >> + ASSERT(mfn_valid(smfn));
> >> + ASSERT(mfn_valid(gmfn));
> >> +
> >> + if ( sp->u.sh.type == SH_type_l1_32_shadow ||
> >> + sp->u.sh.type == SH_type_fl1_32_shadow )
> > Using a switch would also be nice IMO and would avoid some of the code
> > churn.
>
> Good point. Happy to do that if Tim agrees (but I won't bother sending
> a v2 just now).
Sure, feel free to keep my RB after that.
Roger.
next prev parent reply other threads:[~2020-05-21 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 9:04 [PATCH] x86/shadow: Reposition sh_remove_write_access_from_sl1p() Andrew Cooper
2020-05-21 10:12 ` Paul Durrant
2020-05-21 10:26 ` Andrew Cooper
2020-05-21 10:26 ` Roger Pau Monné
2020-05-21 10:32 ` Andrew Cooper
2020-05-21 12:22 ` Roger Pau Monné [this message]
2020-05-24 11:52 ` Tim Deegan
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=20200521111441.GS54375@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--cc=wl@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.