All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Don Dutile <ddutile@redhat.com>,
	Sheng Yang <sheng@linux.intel.com>
Subject: Re: [PATCH 0/12] PV on HVM Xen
Date: Thu, 03 Jun 2010 12:44:54 -0700	[thread overview]
Message-ID: <4C080636.9060508@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1006011435570.3401@kaball-desktop>

On 06/03/2010 06:07 AM, Stefano Stabellini wrote:
> Hi all,
> the last update on the PV on HVM Xen series contains the following
> changes:
>
> - some variables and functions have been renamed following Jeremy's
> suggestions, in particular:
> s/init_shared_info/xen_hvm_init_shared_info
> s/xen_platform_pci/xen_platform_pci_enabled
> s/UNPLUG_/XEN_UNPLUG_
>
> - the two platform_pci.h header files have been merged and the useless
> intro has been removed;
>
> - the xen platform pci product number and driver versions have been made
> static;
>
> - the description on the VIRQ_TIMER patch has been improved;
>
> - a new patch to fix hpet behaviour has been introduced: hpet_disable is
> called unconditionally on machine shutdown, and doesn't check whether
> hpet has been actually enabled, causing trouble if it hasn't;
>
> - the vector callback patch has been improved: we don't use the ipi
> vector anymore but we allocate our own so that we can avoid useless and
> expensive vlapic acks.
>   

I think they're worse than that; I think they could end up potentially
acking a pending interrupt which hasn't been delivered yet.

>
> Meanwhile the vector callback patch for xen has been checked into
> xen-unstable, so you don't need a separate patch for xen anymore to take
> full advantage of this patch series.
>
> A git tree is available here:
>
> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
>
> branch name 2.6.34-pvhvm-v3.
>   

Thanks,

    J

  reply	other threads:[~2010-06-03 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 13:07 [PATCH 0/12] PV on HVM Xen Stefano Stabellini
2010-06-03 19:44 ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-21 16:12 Stefano Stabellini
2010-06-21 16:12 ` Stefano Stabellini
2010-06-21 16:14 ` Stefano Stabellini
2010-06-21 16:14   ` Stefano Stabellini
2010-06-30 17:56 ` Konrad Rzeszutek Wilk
2010-07-01 11:38   ` 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=4C080636.9060508@goop.org \
    --to=jeremy@goop.org \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=ddutile@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.