All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-ia64-devel <xen-ia64-devel@lists.xensource.com>,
	Ewan Mellor <ewan@xensource.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [PATCH] architecture-specific stuff in xend
Date: Thu, 10 Aug 2006 22:27:50 +0100	[thread overview]
Message-ID: <20060810212750.GA7202@totally.trollied.org> (raw)
In-Reply-To: <1155244357.2833.23.camel@basalt.austin.ibm.com>

On Thu, Aug 10, 2006 at 04:12:37PM -0500, Hollis Blanchard wrote:

> John, would you extend this scheme to cover host OS differences? I think

I think it makes sense to use a parallel scheme of xen/xend/host/ for
those parameters. That is, the way you've done this looks good to me.

> tools/python/xen/util/Brctl.py, wouldn't it make more sense to replace
> that file entirely depending on the host OS?

Yes. As it is, it's only used for the vnet stuff, which only exists on
Linux, so it's not a super-big problem right now.

thanks
john

  reply	other threads:[~2006-08-10 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 15:34 architecture-specific stuff in xend Hollis Blanchard
2006-08-08 15:59 ` [XenPPC] Re: [Xen-devel] " John Levon
2006-08-08 16:15   ` Hollis Blanchard
2006-08-08 17:12     ` John Levon
2006-08-09  9:28   ` Ewan Mellor
2006-08-09 15:07     ` Hollis Blanchard
2006-08-09 16:18       ` Ewan Mellor
2006-08-10 21:12         ` [PATCH] " Hollis Blanchard
2006-08-10 21:27           ` John Levon [this message]
2006-08-11 22:59           ` Daniel Miles
2006-08-14 17:40         ` Hollis Blanchard
2006-08-15  2:14           ` Hollis Blanchard

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=20060810212750.GA7202@totally.trollied.org \
    --to=levon@movementarian.org \
    --cc=ewan@xensource.com \
    --cc=hollisb@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=xen-ppc-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.