From: Sheng Yang <sheng@linux.intel.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH][v2] Hybrid extension support in Xen
Date: Wed, 3 Feb 2010 13:15:06 +0800 [thread overview]
Message-ID: <201002031315.06684.sheng@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002021639270.22615@kaball-desktop>
On Wednesday 03 February 2010 02:27:42 Stefano Stabellini wrote:
> On Tue, 2 Feb 2010, Sheng Yang wrote:
> > Well, for us, we want evtchn because we want to improve interrupt
> > intensive passthru device's performance(though too big for the first
> > step, we have experiment patches, but would like to consolidate with the
> > solution of pv_ops dom0). The situation won't change if we still use
> > emulated APIC path...
>
> I think you should keep this as the last step: once you have all the
> other PV features working on HVM like Ian suggested, send a patch to
> allow a guest kernel to switch from emulated APIC to evtchn for every
> device.
> If you manage to keep it simple, it could be a win for everyone.
>
Make event channel coexist with IOAPIC/LAPIC is quite different from what we
are doing now, and Xen already have PV-on-HVM for that.
Of course, I also want to have a elegant solution in the end, so I would try
hard to keep things simple, and keep the code clear.
--
regards
Yang, Sheng
next prev parent reply other threads:[~2010-02-03 5:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 8:16 [PATCH][v2] Hybrid extension support in Xen Sheng Yang
2010-02-02 11:22 ` Ian Campbell
2010-02-02 12:54 ` Sheng Yang
2010-02-02 13:19 ` Ian Campbell
2010-02-02 13:28 ` Sheng Yang
2010-02-02 13:50 ` Ian Campbell
2010-02-02 14:00 ` Tim Deegan
2010-02-02 14:22 ` Sheng Yang
2010-02-02 14:28 ` Sheng Yang
2010-02-02 13:35 ` Keir Fraser
2010-02-02 13:52 ` Sheng Yang
2010-02-02 14:01 ` Keir Fraser
2010-02-02 14:13 ` Sheng Yang
2010-02-02 11:26 ` Ian Campbell
2010-02-02 13:06 ` Sheng Yang
2010-02-02 13:52 ` Ian Campbell
2010-02-02 14:04 ` Stefano Stabellini
2010-02-02 14:07 ` Sheng Yang
2010-02-02 16:15 ` Ian Campbell
2010-02-02 16:31 ` Sheng Yang
2010-02-02 18:03 ` Ian Campbell
2010-02-02 18:27 ` Stefano Stabellini
2010-02-03 5:15 ` Sheng Yang [this message]
2010-02-03 10:39 ` Tim Deegan
2010-02-02 11:32 ` Paul Durrant
2010-02-02 13:23 ` Keir Fraser
2010-02-02 13:37 ` Sheng Yang
2010-02-02 14:03 ` Keir Fraser
2010-02-02 14:08 ` Sheng Yang
2010-02-02 14:32 ` Keir Fraser
2010-02-02 14:37 ` Keir Fraser
2010-02-02 15:51 ` Sheng Yang
2010-02-02 14:39 ` Sheng Yang
2010-02-02 13:52 ` Ian Campbell
2010-02-02 13:53 ` 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=201002031315.06684.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.