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 V3 2/6]: PVH: use native irq, enable callback, use HVM ring ops, smp, ...
Date: Thu, 18 Oct 2012 15:03:59 -0700 [thread overview]
Message-ID: <20121018150359.794768d2@mantra.us.oracle.com> (raw)
In-Reply-To: <1350557077.2460.113.camel@zakaz.uk.xensource.com>
On Thu, 18 Oct 2012 11:44:37 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-10-18 at 01:30 +0100, Mukesh Rathor wrote:
> > PVH: make gdt_frames[]/gdt_ents into a union with {gdtaddr, gdtsz},
> > PVH only needs to send down gdtaddr and gdtsz. irq.c: PVH uses
> > native_irq_ops. vcpu hotplug is currently not available for PVH.
> > events.c: setup callback vector for PVH. smp.c: This pertains to
> > bringing up smp vcpus. PVH runs in ring 0, so syscalls are native.
> > Also, the vcpu context is send down via the hcall to be set in the
> > vmcs. gdtaddr and gdtsz are unionionized as PVH only needs to send
> > these two to be set in the vmcs. Finally, PVH ring ops uses HVM
> > paths for xenbus.
> >
> > Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
> > ---
> > arch/x86/include/asm/xen/interface.h | 11 +++++-
> > arch/x86/xen/irq.c | 5 ++-
> > arch/x86/xen/p2m.c | 2 +-
> > arch/x86/xen/smp.c | 75
> > ++++++++++++++++++++++------------ drivers/xen/cpu_hotplug.c
> > | 4 +- drivers/xen/events.c | 9 ++++-
> > drivers/xen/xenbus/xenbus_client.c | 3 +-
>
> This patch seems to have been horribly whitespace damaged.
Hmm.. not sure what happened. Resending. See another email.
> Have you seen "git send-email" ? It's very useful for avoiding this
> sort of thing and also takes a lot of the grunt work out of reposting
> a series.
> It also chains the patches as replies to the introductory zero-th mail
> -- which is something I've been meaning to ask you to do for a while.
> It's useful because it joins the series together in a thread which
> makes it easier to keep track of in my INBOX.
I prefer different thread-sets for different version. Otherwise too
many emails makes much harder to manage and figure. Besides, as
comments come in, path x of y, may contain different files/changes in
a subsequent version.
thanks
Mukesh
next prev parent reply other threads:[~2012-10-18 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 0:30 Mukesh Rathor
2012-10-18 10:44 ` [Xen-devel] " Ian Campbell
2012-10-18 22:03 ` Mukesh Rathor [this message]
2012-10-19 6:47 ` Ian Campbell
2012-10-18 22:38 ` [Xen-devel] [PATCH V3 2/6]: (RESEND) " Mukesh Rathor
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=20121018150359.794768d2@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®