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: xen-devel@lists.xensource.com
Subject: Re: PV on HVM
Date: Mon, 10 May 2010 13:47:11 -0700	[thread overview]
Message-ID: <4BE870CF.5050004@goop.org> (raw)
In-Reply-To: <4BE86F4D.1060500@goop.org>

On 05/10/2010 01:40 PM, Jeremy Fitzhardinge wrote:
> On 05/10/2010 07:20 AM, Stefano Stabellini wrote:
>   
>> Hi all,
>> this is the updated version of the PV on HVM series: many bugs have been
>> fixed and VIRQ_TIMER support has been added.
>> In order to be able to use VIRQ_TIMER and to improve performances you
>> need two other patches to Xen to implement the vector callback mechanism
>> for event channel delivery and to export some time related hypercalls to
>> HVM guests too.
>>
>> This series is based on a standard 2.6.32 tree, a git tree is also
>> available here:
>>
>> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
>>
>> branch name 2.6.32-pvhvm.
>>   
>>     
> I'm confused.  These patches don't seem to correspond with that branch. 
> Are these the same as the branch but rearranged, or something else?
>   

I see, it looks like the condensed version of the branch.  I really
prefer you'd keep the patches incremental: its much easier to review the
incremental changes rather than folding updates into the
already-reviewed base patches.  Folding down is a late-stage process for
submission, and not something that should be done prematurely.

    J

  reply	other threads:[~2010-05-10 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 14:20 PV on HVM Stefano Stabellini
2010-05-10 14:45 ` Alex Bligh
2010-05-10 14:58   ` Stefano Stabellini
2010-05-10 15:38     ` Alex Bligh
2010-05-10 20:40 ` Jeremy Fitzhardinge
2010-05-10 20:47   ` Jeremy Fitzhardinge [this message]
2010-05-11 11:10     ` 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=4BE870CF.5050004@goop.org \
    --to=jeremy@goop.org \
    --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.