linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	Ingo Molnar <mingo@elte.hu>,
	Konrad Rzeszutek Wilk <kliw@darnok.org>
Subject: Re: [Xen-devel] [PATCH 7/7] xen: Enable event channel of PV extension of HVM
Date: Wed, 10 Mar 2010 10:56:42 +0800	[thread overview]
Message-ID: <201003101056.42511.sheng@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003090954010.4869@kaball-desktop>

On Tuesday 09 March 2010 18:22:31 Stefano Stabellini wrote:
> On Tue, 9 Mar 2010, Ian Campbell wrote:
> > On Tue, 2010-03-09 at 07:00 +0000, Jeremy Fitzhardinge wrote:
> > > On 03/08/2010 05:53 PM, Sheng Yang wrote:
> > > > On Tuesday 09 March 2010 01:10:56 Stefano Stabellini wrote:
> > > >> I think that mapping interrupts into VIRQs is a bad idea: you should
> > > >> map interrupts into pirqs instead, the code exists already on the
> > > >> kernel side so we don't need to do any (ugly) change ther.
> > > >
> > > > The code existed in the pv_ops dom0 side, but not in the upstream
> > > > Linux. The latter is our target. We want this work to be accepted by
> > > > upstream Linux soon.
> > >
> > >    2. It has significant overlaps with the current xen.git development
> > >       which is also targeted for upstream.  There's no point in
> > > creating an unnecessary duplicate mechanism when the infrastructure
> > > will be in place anyway.
> >
> > There's also nothing stopping us from upstreaming portions of the "dom0"
> > patchset ahead of full dom0 support if it is useful for some domU
> > feature.
> 
> Indeed.
> You just need the pirq mappings and few other things, it shouldn't be
> too hard.
> At this point I am going to do that myself after this patch series is
> completed.
 
I think we can leave the controversial thing later. At least, we want a 
framework for PV extension of HVM. We can work together to determine what is 
the better way for evtchn, as well as porting pirqs. (And the later MSI work 
may also depends on it)

But I think the former 6 patches can be taken as the base. It won't overlapped 
with others. And PV clocksource is definitely important for HVM guest. We 
would like to get the first 6 ones checked in Linux upstream first, then we 
can work on others. And it would the work easier for us later.

So Jeremy, how about a even more simplified version only contained framework 
and pv clocksource? I think it's pretty elegant and solid first step into 
Linux upstream.

If you agree, I would send the updated patchset soon, only framework and pv 
clocksource.

-- 
regards
Yang, Sheng

  parent reply	other threads:[~2010-03-10  2:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08  7:18 [PATCH 0/7][v7] PV extension of HVM (Hybrid) for Xen Sheng Yang
2010-03-08  7:18 ` [PATCH 1/7] xen: add support for hvm_op Sheng Yang
2010-03-08  7:18 ` [PATCH 2/7] xen: Import cpuid.h from Xen Sheng Yang
2010-03-08  7:18 ` [PATCH 3/7] xen: Make pv drivers only work with xen_pv_domain() Sheng Yang
2010-03-08  7:18 ` [PATCH 4/7] xen/hvm: Xen PV extension of HVM initialization Sheng Yang
2010-03-08  7:18 ` [PATCH 5/7] x86/xen: The entrance for PV extension of HVM Sheng Yang
2010-03-08  7:18 ` [PATCH 6/7] xen: Enable PV clocksource for HVM Sheng Yang
2010-03-08  7:18 ` [PATCH 7/7] xen: Enable event channel of PV extension of HVM Sheng Yang
2010-03-08 17:00   ` [Xen-devel] " Stefano Stabellini
2010-03-09  1:23     ` Sheng Yang
2010-03-08 17:10   ` Stefano Stabellini
2010-03-09  1:53     ` Sheng Yang
2010-03-09  7:00       ` Jeremy Fitzhardinge
2010-03-09  9:48         ` Ian Campbell
2010-03-09 10:22           ` Stefano Stabellini
2010-03-09 19:26             ` Jeremy Fitzhardinge
2010-03-10  3:08               ` Konrad Rzeszutek Wilk
2010-03-10  2:56             ` Sheng Yang [this message]
2010-03-10 15:29               ` Stefano Stabellini
2010-03-11  1:34                 ` Sheng Yang
2010-03-11 11:43                   ` Stefano Stabellini
2010-03-12  1:23                     ` Sheng Yang
2010-03-12 10:47                       ` Stefano Stabellini
  -- strict thread matches above, loose matches on Subject: below --
2010-03-05  6:07 [PATCH 0/7][v6] PV extension of HVM (Hybrid) for Xen Sheng Yang
2010-03-05  6:07 ` [PATCH 7/7] xen: Enable event channel of PV extension of HVM Sheng Yang
2010-03-08 22:16   ` [Xen-devel] " Jeremy Fitzhardinge
2010-03-09  5:55     ` Sheng Yang

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=201003101056.42511.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=kliw@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).