From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [PATCH 10/18 V2]: PVH xen: introduce vmx_pvh.c and pvh.c
Date: Tue, 2 Apr 2013 18:45:29 -0700 [thread overview]
Message-ID: <20130402184529.4e0e9f63@mantra.us.oracle.com> (raw)
In-Reply-To: <20130402141012.GB1754@phenom.dumpdata.com>
On Tue, 2 Apr 2013 10:10:12 -0400
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Mon, Apr 01, 2013 at 06:26:45PM -0700, Mukesh Rathor wrote:
> > On Mon, 18 Mar 2013 12:32:06 -0400
> > Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > >
> > > > +}
> > > > +
> > > > +typedef unsigned long pvh_hypercall_t(
> > > > + unsigned long, unsigned long, unsigned long, unsigned long,
> > > > unsigned long,
> > > > + unsigned long);
> > >
> > > No way to re-use the something standard? I am not sure what is
> > > 'PVH' specific to it? It looks like a garden variety normal
> > > hypercalls.
> >
> > It does use standard do_xx calls, PV goes thru it's own table, HVM
> > thru its own, and PVH thru its own. This was suggested to me early
> > on, and it's easier this way since HVM and PVH are not same hcalls.
>
> I meant the typedef.
Ok, I could move the hvm_typedef* to header, and use that. no biggie.
next prev parent reply other threads:[~2013-04-03 1:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 0:41 [PATCH 10/18 V2]: PVH xen: introduce vmx_pvh.c and pvh.c Mukesh Rathor
2013-03-18 12:16 ` Jan Beulich
2013-04-02 0:08 ` Mukesh Rathor
2013-04-02 7:00 ` Jan Beulich
2013-03-18 16:32 ` Konrad Rzeszutek Wilk
2013-04-02 1:26 ` Mukesh Rathor
2013-04-02 14:10 ` Konrad Rzeszutek Wilk
2013-04-03 1:29 ` Mukesh Rathor
2013-04-03 14:40 ` Konrad Rzeszutek Wilk
2013-04-03 1:45 ` Mukesh Rathor [this message]
2013-04-03 1:42 ` Mukesh Rathor
2013-04-04 1:01 ` Mukesh Rathor
2013-04-04 8:23 ` Jan Beulich
2013-03-21 16:49 ` Tim Deegan
2013-03-22 8:32 ` Jan Beulich
2013-03-22 10:06 ` Tim Deegan
2013-04-03 1:37 ` Mukesh Rathor
2013-04-03 8:06 ` Jan Beulich
2013-04-03 23:38 ` Mukesh Rathor
2013-04-04 9:12 ` Tim Deegan
2013-04-04 23:00 ` 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=20130402184529.4e0e9f63@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
/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).