From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.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 0 of 5] PV on HVM Xen
Date: Wed, 10 Mar 2010 17:55:40 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1003101739480.28412@kaball-desktop> (raw)
In-Reply-To: <20100310173339.GO1878@reaktio.net>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On Wed, 10 Mar 2010, Pasi Kärkkäinen wrote:
> On Wed, Mar 10, 2010 at 03:46:54PM +0000, Stefano Stabellini wrote:
> > Hi all,
> > this is a reduced and rebased version of the patch series I sent
> > yesterday "enhanced PV on HVM": this series is based on Linux 2.5.32 and
> > can be applied now, it includes everything but the pirq remapping
> > related functions that are not ready to be upstreamed at the moment.
> >
> > Therefore it just achieves the goal of enabling PV devices in Linux
> > running in a Xen HVM domain, it doesn't allow event channels delivery in
> > place of interrupts.
> >
> > The patch series consists of 5 patches, each patch comes with a detailed
> > description.
> > In order for this to work we also need a patch for Xen, that is being
> > worked on as we speak.
> >
>
> Hmm.. is it possible to get PV-on-HVM drivers working on older Xen versions,
> that don't have additional patches?
>
> Just like the unmodified_drivers works for 2.6.18 and 2.6.27.
>
The problem is that the old unmodified_drivers use a normal interrupt
from the xen pci platform device to receive event channels, and this
doesn't play well with the idea of remapping all the interrupts with
event channels, that is one if the main goals of the previous "enhanced"
patch series.
For this reason the new PV on HVM patch series sets up a new vector
based callback mechanism.
However it might be still possible to provide an additional, backward
compatible, delivery mechanism in case the new one fails.
I'll try to explore this option.
next prev parent reply other threads:[~2010-03-10 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 15:46 Stefano Stabellini
2010-03-10 17:33 ` [Xen-devel] " Pasi Kärkkäinen
2010-03-10 17:55 ` Stefano Stabellini [this message]
2010-03-10 19:45 ` Jeremy Fitzhardinge
2010-03-12 3:23 ` Sheng Yang
2010-03-12 10:42 ` Stefano Stabellini
2010-03-12 21:53 ` Jeremy Fitzhardinge
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.1003101739480.28412@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasik@iki.fi \
--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®