From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2 of 9 v2] libxl: add support for image files for NetBSD
Date: Fri, 18 Nov 2011 15:49:44 +0100 [thread overview]
Message-ID: <CAPLaKK5drHeZPOCsSro0d57z0r8o19p4so3VECcE2R5URAyy5w@mail.gmail.com> (raw)
In-Reply-To: <1321622877.3664.344.camel@zakaz.uk.xensource.com>
2011/11/18 Ian Campbell <Ian.Campbell@citrix.com>:
> On Fri, 2011-11-18 at 11:59 +0000, Roger Pau Monne wrote:
>> # HG changeset patch
>> # User Roger Pau Monne <roger.pau@entel.upc.edu>
>> # Date 1317386335 -7200
>> # Node ID 9e8abd626484f82a95d0edc07834ae287bc9467a
>> # Parent 23578c9942bcc8767adc4e435bb1fd1cd89f5e18
>> libxl: add support for image files for NetBSD
>>
>> Created a helper function to detect if the OS is capable of using
>> image files as phy backends. Create two OS specific files, and
>> changed the Makefile to choose the correct one at compile time.
>>
>> Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu>
>>
>> diff -r 23578c9942bc -r 9e8abd626484 tools/libxl/Makefile
>> --- a/tools/libxl/Makefile Fri Sep 30 14:38:55 2011 +0200
>> +++ b/tools/libxl/Makefile Fri Sep 30 14:38:55 2011 +0200
>> @@ -32,6 +32,12 @@ endif
>> LIBXL_OBJS-$(CONFIG_X86) += libxl_cpuid.o
>> LIBXL_OBJS-$(CONFIG_IA64) += libxl_nocpuid.o
>>
>> +ifeq ($(CONFIG_NetBSD),y)
>> +LIBXL_OBJS-y += libxl_phybackend.o
>> +else
>> +LIBXL_OBJS-y += libxl_nophybackend.o
>
> phy vs nophy don't really make sense to me here, since in both cases the
> content relates to the phy backend.
>
> Perhaps we need libxl_$(OS).c to contain os specific stuff?
A libxl_$(OS).c sounds interesting, I could put hotplug and backend OS
specific code there, but I'm afraid it might get crowded and become
difficult to understand. If I don't receive any other suggestions, I
will create a libxl_netbsd.c and libxl_linux.c (and libxl_solaris.c?)
and place the hotplug and backend helper functions there.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-11-18 14:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 11:59 [PATCH 0 of 9 v2] libxl: add support for hotplug script calling from libxl Roger Pau Monne
2011-11-18 11:59 ` [PATCH 1 of 9 v2] xenbackendd: pass type of block device to hotplug script Roger Pau Monne
2011-11-18 11:59 ` [PATCH 2 of 9 v2] libxl: add support for image files for NetBSD Roger Pau Monne
2011-11-18 13:27 ` Ian Campbell
2011-11-18 14:49 ` Roger Pau Monné [this message]
2011-11-18 15:20 ` Ian Campbell
2011-11-18 11:59 ` [PATCH 3 of 9 v2] libxl: add libxl__forkexec function to libxl_exec Roger Pau Monne
2011-11-18 13:31 ` Ian Campbell
2011-11-18 14:50 ` Roger Pau Monné
2011-11-24 18:11 ` Ian Jackson
2011-12-01 14:29 ` Roger Pau Monné
2011-12-01 14:57 ` Ian Jackson
2011-11-18 11:59 ` [PATCH 4 of 9 v2] libxl: introduce libxl__wait_for_device_state Roger Pau Monne
2011-11-18 13:34 ` Ian Campbell
2011-11-18 11:59 ` [PATCH 5 of 9 v2] libxl: wait for devices to initialize upon addition to the domain Roger Pau Monne
2011-11-18 13:38 ` Ian Campbell
2011-11-18 14:58 ` Roger Pau Monné
2011-11-18 11:59 ` [PATCH 6 of 9 v2] libxl: execute hotplug scripts directly from libxl Roger Pau Monne
2011-11-18 13:42 ` Ian Campbell
2011-11-21 11:42 ` Roger Pau Monné
2011-11-21 14:36 ` Ian Campbell
2011-11-24 12:19 ` Ian Campbell
2011-12-01 8:44 ` Roger Pau Monné
2011-11-18 11:59 ` [PATCH 7 of 9 v2] hotplug NetBSD: detach devices when state is 5 or 6 Roger Pau Monne
2011-11-18 11:59 ` [PATCH 8 of 9 v2] hotplug: remove debug messages from NetBSD hotplug scripts Roger Pau Monne
2011-11-18 11:59 ` [PATCH 9 of 9 v2] rc.d NetBSD: don't start xenbackendd by default, only when xend needs it Roger Pau Monne
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=CAPLaKK5drHeZPOCsSro0d57z0r8o19p4so3VECcE2R5URAyy5w@mail.gmail.com \
--to=roger.pau@entel.upc.edu \
--cc=Ian.Campbell@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).