From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
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 15:29:30 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1003101452540.28412@kaball-desktop> (raw)
In-Reply-To: <201003101056.42511.sheng@linux.intel.com>
On Wed, 10 Mar 2010, Sheng Yang wrote:
> 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)
>
Most of my patch series can be upstreamed right now, the only thing that
needs some extra work is the pirq remapping.
So yes, we can upstream the rest and that would also make PV on HVM work
on linux upstream ASAP.
I think that is a worthy goal by itself, therefore I am going to send
another reduced patch series, ready to be upstreamed, without pirq
remappings, with support for PV on HVM.
next prev parent reply other threads:[~2010-03-10 15:25 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
2010-03-10 15:29 ` Stefano Stabellini [this message]
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=alpine.DEB.2.00.1003101452540.28412@kaball-desktop \
--to=stefano.stabellini@eu.citrix.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=sheng@linux.intel.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
all inboxes | Powered by JetHome®