All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ling, Xiaofeng" <xiaofeng.ling@intel.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Khoa Huynh <khoa@us.ibm.com>,
	xen-devel@lists.xensource.com, "Shi,
	Kuiliang" <kuiliang.shi@intel.com>,
	xen-devel-bounces@lists.xensource.com
Subject: Re: VMX status daily report Nov. 3
Date: Mon, 07 Nov 2005 09:52:52 +0800	[thread overview]
Message-ID: <436EB374.4000206@intel.com> (raw)
In-Reply-To: <20051103154431.GN408@leeni.uk.xensource.com>

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

Ewan Mellor wrote:
> On Thu, Nov 03, 2005 at 09:35:37AM -0600, Khoa Huynh wrote:
> 
> 
>>"Shi, Kuiliang" <kuiliang.shi@intel.com> wrote on 11/03/2005 03:14:46 AM:
>>
>>
>>>
>>>We have test latest xen (ChangeSet 7608) on VT platform with Intel 915
>>>chipset and Here is the test summary:
>>>
> 
> This patch breaks vifs for everyone else (vif IDs are allocated from 0).  I
> have a replacement ready and waiting to go.
> 
Ewan, how is your replacement patch going on?
Attach is just a simple fix to use "-1" to indicate a ioemu device.
Will that be ok with vif?


[-- Attachment #2: devid-fix.patch --]
[-- Type: text/x-patch, Size: 1257 bytes --]

# HG changeset patch
# User Xiaofeng Ling <xiaofeng.ling@intel.com>
# Node ID ff100cd8f74fd53ad652e5760be956a6631a96d3
# Parent  a969d918674e6deab2a8c61977e4a4016a680ca7
ioemu device for vmx guest doesn't need backend/frontend info in xenstore

Signed-off-by: Xiaofeng Ling <xiaofeng.ling>
diff -r a969d918674e -r ff100cd8f74f tools/python/xen/xend/server/DevController.py
--- a/tools/python/xen/xend/server/DevController.py	Fri Nov  4 16:01:49 2005 +0100
+++ b/tools/python/xen/xend/server/DevController.py	Mon Nov  7 09:46:02 2005 +0800
@@ -58,6 +58,9 @@
         """
         (devid, back, front) = self.getDeviceDetails(config)
 
+        if devid == -1:
+            return devid
+        
         self.writeDetails(config, devid, back, front)
 
         status, fn_ret = self.waitForBackend(devid)
diff -r a969d918674e -r ff100cd8f74f tools/python/xen/xend/server/blkif.py
--- a/tools/python/xen/xend/server/blkif.py	Fri Nov  4 16:01:49 2005 +0100
+++ b/tools/python/xen/xend/server/blkif.py	Mon Nov  7 09:46:02 2005 +0800
@@ -43,7 +43,7 @@
         
         dev = sxp.child_value(config, 'dev')
         if re.match('^ioemu:', dev):
-            return (0,{},{})
+            return (-1,{},{})
 
         devid = blkif.blkdev_name_to_number(dev)
 

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2005-11-07  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  9:14 VMX status daily report Nov. 3 Shi, Kuiliang
2005-11-03 15:35 ` Khoa Huynh
2005-11-03 15:44   ` Ewan Mellor
2005-11-04 20:20     ` Khoa Huynh
2005-11-07  1:52     ` Ling, Xiaofeng [this message]
2005-11-07  9:55       ` Ewan Mellor
2005-11-07 22:31         ` ioemu patch from Ewan Mellor (was: VMX status report Nov. 2) Khoa Huynh
  -- strict thread matches above, loose matches on Subject: below --
2005-11-04  2:15 VMX status daily report Nov. 3 Shi, Kuiliang

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=436EB374.4000206@intel.com \
    --to=xiaofeng.ling@intel.com \
    --cc=ewan@xensource.com \
    --cc=khoa@us.ibm.com \
    --cc=kuiliang.shi@intel.com \
    --cc=xen-devel-bounces@lists.xensource.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.