qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "christian.limpach@gmail.com" <christian.limpach@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [XEN][RFC PATCH V2 12/17] xl: Add interface to handle qemu disaggregation
Date: Fri, 24 Aug 2012 13:56:21 +0100	[thread overview]
Message-ID: <503779F5.80508@citrix.com> (raw)
In-Reply-To: <1345728617.12501.92.camel@zakaz.uk.xensource.com>

On 08/23/2012 02:30 PM, Ian Campbell wrote:
> On Wed, 2012-08-22 at 13:31 +0100, Julien Grall wrote:
>    
>> This patch modifies libxl interface for qemu disaggregation.
>>      
> I'd rather see the interfaces changes in the same patch as the
> implementation of the new interfaces.
>
>    
>> For the moment, due to some dependencies between devices, we
>> can't let the user choose which QEMU emulate a device.
>>
>> Moreoever this patch adds an "id" field to nic interface.
>> It will be used in config file to specify which QEMU handle
>> the network card.
>>      
> Is domid+devid not sufficient to identify which nic?
>    
Is the user can specify or find devid easily ?
I added "id" because, I would like that the user
can identify without any problem a network
interface.

>> A possible disaggregation is:
>>      - UI: Emulate graphic card, USB, keyboard, mouse, default devices
>>      (PIIX4, root bridge, ...)
>>      - IDE: Emulate disk
>>      - Serial: Emulate serial port
>>      - Audio: Emulate audio card
>>      - Net: Emulate one or more network cards, multiple QEMU can emulate
>>      different card. The emulated card is specified with its nic ID.
>>
>> Signed-off-by: Julien Grall<julien.grall@citrix.com>
>> ---
>>   tools/libxl/libxl.h         |    3 +++
>>   tools/libxl/libxl_types.idl |   15 +++++++++++++++
>>   2 files changed, 18 insertions(+), 0 deletions(-)
>>
>> diff --git a/tools/libxl/libxl.h b/tools/libxl/libxl.h
>> index c614d6f..71d4808 100644
>> --- a/tools/libxl/libxl.h
>> +++ b/tools/libxl/libxl.h
>> @@ -307,6 +307,7 @@ void libxl_cpuid_dispose(libxl_cpuid_policy_list *cpuid_list);
>>   #define LIBXL_PCI_FUNC_ALL (~0U)
>>
>>   typedef uint32_t libxl_domid;
>> +typedef uint32_t libxl_dmid;
>>
>>   /*
>>    * Formatting Enumerations.
>> @@ -478,12 +479,14 @@ typedef struct {
>>       libxl_domain_build_info b_info;
>>
>>       int num_disks, num_nics, num_pcidevs, num_vfbs, num_vkbs;
>> +    int num_dms;
>>
>>       libxl_device_disk *disks;
>>       libxl_device_nic *nics;
>>       libxl_device_pci *pcidevs;
>>       libxl_device_vfb *vfbs;
>>       libxl_device_vkb *vkbs;
>> +    libxl_dm *dms;
>>
>>       libxl_action_on_shutdown on_poweroff;
>>       libxl_action_on_shutdown on_reboot;
>> diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
>> index daa8c79..36c802a 100644
>> --- a/tools/libxl/libxl_types.idl
>> +++ b/tools/libxl/libxl_types.idl
>> @@ -246,6 +246,20 @@ libxl_domain_sched_params = Struct("domain_sched_params",[
>>       ("extratime",    integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_EXTRATIME_DEFAULT'}),
>>       ])
>>
>> +libxl_dm_cap = Enumeration("dm_cap", [
>> +    (1, "UI"), # Emulate all UI + default device
>>      
> What does "default device" equate too?
>    
The following devices:
    - i440fx
    - piix3
    - piix4
    - dma
    - xen apic
    - xen platform


>> +    (2, "IDE"), # Emulate IDE
>> +    (4, "SERIAL"), # Emulate Serial
>> +    (8, "AUDIO"), # Emulate audio
>> +    ])
>> +
>> +libxl_dm = Struct("dm", [
>> +    ("name",         string),
>> +    ("path",         string),
>> +    ("capabilities",   uint64),
>>      
> uint64 and not libxl_dm_cap?
>    
Will be fixed in the next patch version.

-- 
Julien

  reply	other threads:[~2012-08-24 12:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 12:31 [Qemu-devel] [XEN][RFC PATCH V2 00/17] QEMU disaggregation in Xen environment Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 01/17] hvm: Modify interface to support multiple ioreq server Julien Grall
2012-08-23 13:18   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-23 13:26     ` Keir Fraser
2012-08-24 10:33       ` Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 02/17] hvm: Add functions to handle ioreq servers Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 03/17] hvm-pci: Handle PCI config space in Xen Julien Grall
2012-08-23  7:20   ` [Qemu-devel] [Xen-devel] " Jan Beulich
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 04/17] hvm: Change initialization/destruction of an hvm Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 05/17] hvm: Modify hvm_op Julien Grall
2012-08-23  7:27   ` [Qemu-devel] [Xen-devel] " Jan Beulich
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 06/17] hvm-io: IO refactoring with ioreq server Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 07/17] hvm-io: send invalidate map cache to each registered servers Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 08/17] hvm-io: Handle server in buffered IO Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 09/17] xc: Add the hypercall for multiple servers Julien Grall
2012-08-23 13:21   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 10/17] xc: Add argument to allocate more special pages Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 11/17] xc: modify save/restore to support multiple device models Julien Grall
2012-08-23 13:27   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-23 19:13     ` Julien Grall
2012-08-23 19:52       ` Ian Campbell
2012-08-24 10:27         ` Julien Grall
2012-08-24 10:35           ` Ian Campbell
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 12/17] xl: Add interface to handle qemu disaggregation Julien Grall
2012-08-23 13:30   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-24 12:56     ` Julien Grall [this message]
2012-08-24 13:03       ` Ian Campbell
2012-08-24 13:23         ` Julien Grall
2012-08-22 12:31 ` [Qemu-devel] [XEN][RFC PATCH V2 13/17] xl: add device model id to qmp functions Julien Grall
2012-08-22 12:32 ` [Qemu-devel] [XEN][RFC PATCH V2 14/17] xl-parsing: Parse new device_models option Julien Grall
2012-08-23 13:35   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-24 13:12     ` Julien Grall
2012-08-22 12:32 ` [Qemu-devel] [XEN][RFC PATCH V2 15/17] xl: support spawn/destroy on multiple device model Julien Grall
2012-08-23 13:56   ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-08-24 13:51     ` Julien Grall
2012-08-24 14:09       ` Ian Campbell
2012-08-24 14:37         ` Julien Grall
2012-08-24 14:45           ` Ian Campbell
2012-08-22 12:32 ` [Qemu-devel] [XEN][RFC PATCH V2 16/17] xl: Fix PCI library Julien Grall
2012-08-22 12:32 ` [Qemu-devel] [XEN][RFC PATCH V2 17/17] xl: implement save/restore for multiple device models Julien Grall

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=503779F5.80508@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=christian.limpach@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xen.org \
    /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).