mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: topperxin <topperxin@126.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re:[Xen-devel] [PATCH v2 0/6] Xen PV on HVM fixes and improvements
Date: Thu, 3 Mar 2011 15:05:09 +0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1103031502090.2968@kaball-desktop> (raw)
In-Reply-To: <50e6b629.254d.12e798c9072.Coremail.topperxin@126.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Thu, 3 Mar 2011, topperxin wrote:
> Hi stefano,
> 
>    It's very great of your work.I think it't useful 
> to me, I have checked it out, and I will study it.
>   What I care mostly is the pv-on-hvm drivers, now 
> my main work is port pvonhvm drivers to various guest
> OS, no matter what OS version, such as ubuntu 10.10, 
> debian 505 etc. But I found this work is difficult & 
> boring to me, I can't find a general method which can 
> easily port the pvonhvm drivers to all kinds guest os.
> Do you have any good ideas?

PV on HVM is upstream now, so it is just a matter of time before all the
distros will have a kernel that supports PV on HVM out of the box.


>    I found there are not platform-pci source in your 
> project, as we know, in the old pvonhvm drivers version,
> platform-pci module is important, it was used to establish
> the communication mechanism, such as xenbus, evtchn,etc, 
> could you please tell me how can you get rid of it? and how 
> can you substitute platform-pci, with which?

Yes there is:
drivers/xen/platform-pci.c

  parent reply	other threads:[~2011-03-03 15:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 17:11 Stefano Stabellini
2011-02-25 17:11 ` [PATCH v2 1/6] xen: no need to delay xen_setup_shutdown_event for hvm guests anymore stefano.stabellini
2011-02-25 17:11 ` [PATCH v2 2/6] xen: do not use xen_info on HVM, set pv_info name to "Xen HVM" stefano.stabellini
2011-02-25 17:11 ` [PATCH v2 3/6] xen-blkfront: handle Xen major numbers other than XENVBD stefano.stabellini
2011-02-25 17:11 ` [PATCH v2 4/6] xen: make the ballon driver work for hvm domains stefano.stabellini
2011-02-25 17:11 ` [PATCH v2 5/6] xen: PV on HVM: support PV spinlocks and IPIs stefano.stabellini
2011-02-25 17:12 ` [PATCH v2 6/6] xen: fix compile issue if XEN is enabled but XEN_PVHVM is disabled stefano.stabellini
2011-02-25 19:32 ` [PATCH v2 0/6] Xen PV on HVM fixes and improvements Konrad Rzeszutek Wilk
     [not found] ` <50e6b629.254d.12e798c9072.Coremail.topperxin@126.com>
2011-03-03  7:58   ` [Xen-devel] " Pasi Kärkkäinen
2011-03-03 15:05   ` Stefano Stabellini [this message]
     [not found]   ` <7ef859a1.d96b.12e933f972a.Coremail.topperxin@126.com>
2011-03-08 11:17     ` Stefano Stabellini
     [not found]     ` <37633ce9.14869.12e95634727.Coremail.topperxin@126.com>
2011-03-08 12:45       ` Stefano Stabellini

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.1103031502090.2968@kaball-desktop \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=topperxin@126.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®