From: Tamas K Lengyel <tamas.lengyel@zentific.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.5 v9 04/19] xen: Relocate p2m_mem_access_resume to mem_access common
Date: Wed, 24 Sep 2014 16:54:36 +0200 [thread overview]
Message-ID: <CAErYnsi5rssveWKfA+z3sUmBPA2jqA6GiOSn0VRxYXmYHx35ng@mail.gmail.com> (raw)
In-Reply-To: <5422F6E102000078000385FA@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2044 bytes --]
On Wed, Sep 24, 2014 at 4:52 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 24.09.14 at 16:47, <tamas.lengyel@zentific.com> wrote:
> > On Wed, Sep 24, 2014 at 3:42 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >
> >> >>> On 24.09.14 at 15:05, <tamas.lengyel@zentific.com> wrote:
> >> > On Wed, Sep 24, 2014 at 2:19 PM, Jan Beulich <JBeulich@suse.com>
> wrote:
> >> >> >>> On 24.09.14 at 11:09, <tklengyel@sec.in.tum.de> wrote:
> >> >> > --- a/xen/arch/x86/mm/p2m.c
> >> >> > +++ b/xen/arch/x86/mm/p2m.c
> >> >> > @@ -1382,6 +1382,60 @@ static void
> >> >> p2m_mem_event_fill_regs(mem_event_request_t *req)
> >> >> > req->x86_regs.cs_arbytes = seg.attr.bytes;
> >> >> > }
> >> >> >
> >> >> > +void p2m_mem_event_emulate_check(struct vcpu *v, const
> >> >> mem_event_response_t *rsp)
> >> >> > +{
> >> >> > + /* Mark vcpu for skipping one instruction upon rescheduling.
> */
> >> >> > + if ( rsp->flags & MEM_EVENT_FLAG_EMULATE )
> >> >> > + {
> >> >> > + struct domain *d = v->domain;
> >> >> > + xenmem_access_t access;
> >> >> > + bool_t violation = 1;
> >> >> > +
> >> >> > + if ( p2m_get_mem_access(d, rsp->gfn, &access) == 0 )
> >> >>
> >> >> While it's certainly not wrong, I personally dislike such single use
> >> >> local variables - you could easily (and without hampering
> readability)
> >> >> pass v->domain here.
> >> >>
> >> >
> >> > Certainly. Does it worth another resend?
> >>
> >> Actually (correcting my earlier reply) I think together with the missed
> >> Cc-s on both v9 patches, re-sending would be desirable, in which
> >> case the cosmetic change above should be done at once.
> >
> > According to get_maintainer I only missed Tim from the original cc list.
> I
> > don't want to spam other maintainers with just these updates, so do you
> see
> > anyone else that should be on this?
>
> IanC as another ARM maintainer? (And Tim is really kind of important
> to Cc here.)
>
> Jan
>
OK, IanC is not popping up for these patches via get_maintainer for some
reason..
Tamas
[-- Attachment #1.2: Type: text/html, Size: 3342 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-09-24 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:09 [PATCH for-4.5 v9 04/19] xen: Relocate p2m_mem_access_resume to mem_access common Tamas K Lengyel
2014-09-24 9:09 ` [PATCH for-4.5 v9 06/19] xen: Relocate mem_event_op domctl and access_op memop into common Tamas K Lengyel
2014-09-24 12:22 ` Jan Beulich
2014-09-24 13:07 ` Tamas K Lengyel
2014-09-24 12:19 ` [PATCH for-4.5 v9 04/19] xen: Relocate p2m_mem_access_resume to mem_access common Jan Beulich
2014-09-24 13:05 ` Tamas K Lengyel
2014-09-24 13:33 ` Jan Beulich
2014-09-24 13:42 ` Jan Beulich
2014-09-24 14:47 ` Tamas K Lengyel
2014-09-24 14:52 ` Jan Beulich
2014-09-24 14:54 ` Tamas K Lengyel [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=CAErYnsi5rssveWKfA+z3sUmBPA2jqA6GiOSn0VRxYXmYHx35ng@mail.gmail.com \
--to=tamas.lengyel@zentific.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@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).