All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] linux/netback: save interrupt state in add_to_net_schedule_list_tail
Date: Wed, 15 Sep 2010 13:58:13 -0700	[thread overview]
Message-ID: <4C913365.7020107@goop.org> (raw)
In-Reply-To: <4C8F5C020200007800015F58@vpn.id2.novell.com>

 On 09/14/2010 02:26 AM, Jan Beulich wrote:
> Nor can I foresee when the pv-ops tree will be reliable enough
> and sufficiently functionally complete (without hacks that in
> some cases I think are worse than those in the 2.6.18 tree) to
> be used as the basis of an enterprise Dom0 (which is the
> criteria that could make us finally do the long hoped for switch).
>

I'd be interested to know what you have in mind here.

    J

  parent reply	other threads:[~2010-09-15 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 13:56 [PATCH] linux/netback: save interrupt state in add_to_net_schedule_list_tail Jan Beulich
2010-09-13 14:14 ` Ian Campbell
2010-09-13 14:38   ` Jan Beulich
2010-09-14  9:12     ` Ian Campbell
2010-09-14  9:26       ` Jan Beulich
2010-09-14 10:00         ` Ian Campbell
2010-09-14 20:34           ` xen.org kernel trees Pasi Kärkkäinen
2010-09-15 20:58         ` Jeremy Fitzhardinge [this message]
2010-09-16  7:18           ` Re: [PATCH] linux/netback: save interrupt state in add_to_net_schedule_list_tail Jan Beulich

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=4C913365.7020107@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.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.