From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH V2 2/7]: PVH: use native irq, enable callback, use HVM ring ops, ...
Date: Tue, 16 Oct 2012 15:11:08 -0700 [thread overview]
Message-ID: <20121016151108.0d30e7cf@mantra.us.oracle.com> (raw)
In-Reply-To: <1350291497.18058.5.camel@zakaz.uk.xensource.com>
On Mon, 15 Oct 2012 09:58:17 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Fri, 2012-10-12 at 20:06 +0100, Mukesh Rathor wrote:
> > On Fri, 12 Oct 2012 09:52:17 +0100
> > Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >
> > > > drivers/xen/cpu_hotplug.c | 4 +++-
> > > > drivers/xen/events.c | 9 ++++++++-
> > > > drivers/xen/xenbus/xenbus_client.c | 3 ++-
> > > > 7 files changed, 27 insertions(+), 8 deletions(-)
> > > >
> > > union {
> > > struct {
> > > unsigned long gdt_frames[16], gdt_ents;
> > > } pv;
> > > struct {
> > > unsigned long gdtaddr, gdtsz;
> > > } pvh;
> > > } gdt;
> > >
> > > (I've gone with naming the union gdt instead of u. You might want
> > > therefore to also drop the gdt prefix from the members?)
> >
> > Is it worth it, I mean, making it a union. Would you be OK if I just
> > used gdt_frames[0] and gdt_ends for gdtaddr and size?
>
> What's the problem with making it a union? Seems like you are 80% of
> the way there.
No problem. It resutls in a patch on xen side too. I'll send that too.
> units AFAICT and so can be combined.
>
> How come you don't need the same stuff for ldt*?
Happens natively. Isn't PVH great!
thanks
mukesh
prev parent reply other threads:[~2012-10-16 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 21:57 Mukesh Rathor
2012-10-12 8:52 ` [Xen-devel] " Ian Campbell
2012-10-12 19:06 ` Mukesh Rathor
2012-10-15 8:58 ` Ian Campbell
2012-10-16 22:11 ` Mukesh Rathor [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=20121016151108.0d30e7cf@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®