All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Roger Pau Monné" <roger.pau@entel.upc.edu>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxl: added libxl compatibility with	physical backend file for NetBSD
Date: Fri, 22 Jul 2011 15:46:04 +0200	[thread overview]
Message-ID: <4E297F1C.5020304@amd.com> (raw)
In-Reply-To: <1311341983.12772.66.camel@zakaz.uk.xensource.com>

On 07/22/11 15:39, Ian Campbell wrote:
> On Fri, 2011-07-22 at 13:38 +0100, Roger Pau Monné wrote:
>> Hello,
>>
>> This patch fixes the problems described in a previous thread regarding
>> PV machines not booting on NetBSD with libxl toolstack. The patch also
>> prevents libxl from adding PCI entries to xenstore if there is no PCI
>> device configured in the guest.
>
> Thanks Roger.
>
> In general we prefer to see individual fixes split up into separate
> patches for review and commit. Also please can you add to your ~/.hgrc:
>          [diff]
>          showfunc = True
> It prints the function name in the hunk header which makes it easier to
> review.
>
> The change to the hotplug script seems odd, if the "xtype" paramter is
> not needed then just remove it altogether, otherwise we need to teach
> libxl what to write.
>
> The PCI change looks good, although you might as well throw the for()
> loop under the check too.
>
> "#ifdef" etc should be in column 0, but the content should be indented
> normally.

Ack.

> The checks on LIBXL_DISK_FORMAT_EMPTY and S_ISBLK are not really related
> so I would not combine them even though the return is the same.
> Otherwise the HAVE_PHY_BACKEND_FILE_SUPPORT change itself looks ok
>
> What is DONT_REMOVE_VBD_FROM_STORE for? Is this because xenbackendd does
> it for you or something else?

The hotplug script invoked by xenbackendd removes the vbd entry
via xenstored-rm.

> Does your changed xenbackendd still work with xend? Oh, I see what the
> hotplug script change was about now -- I guess just remove the commented
> out line?

Ack.

Christoph

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-07-22 13:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 12:38 [PATCH] libxl: added libxl compatibility with physical backend file for NetBSD Roger Pau Monné
2011-07-22 13:25 ` Christoph Egger
2011-07-22 13:39 ` Ian Campbell
2011-07-22 13:46   ` Christoph Egger [this message]
2011-07-22 13:54     ` Ian Campbell
2011-07-22 14:55   ` Roger Pau Monné
  -- strict thread matches above, loose matches on Subject: below --
2011-07-22 17:36 Roger Pau Monne
2011-07-22 16:01 ` Ian Campbell
2011-07-22 17:07   ` Roger Pau Monné
2011-07-22 19:07     ` Ian Campbell
2011-07-29 11:02       ` Roger Pau Monné

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=4E297F1C.5020304@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=roger.pau@entel.upc.edu \
    --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.