All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Li, Haicheng" <haicheng.li@intel.com>,
	"Xu, Dongxiao" <dongxiao.xu@intel.com>,
	xen-devel@lists.xensource.com
Subject: Re: VMX status report. Xen: #17630 & Xen0: #540 -- blocked
Date: Thu, 15 May 2008 13:54:49 +0200	[thread overview]
Message-ID: <482C2489.6050709@suse.de> (raw)
In-Reply-To: <18476.6533.343767.167852@mariner.uk.xensource.com>

Ian Jackson schrieb:
 > Could those of you having this problem please try the attached patch ?
 > I have tested this one much more thoroughly :-/.

It works for me, I don't like it though. Maybe I don't understand 
correctly what the intent of the whole protocol stuff was. But if I do, 
I think you're destroying this with your patch. This is not necessarily 
bad as we don't use it anyway. But then it would be much cleaner to 
remove the functionality altogether.

To be a bit more concrete, I think the following change is wrong (even 
if there is no user anyway):

-    /* no need to test disk image formats for vvfat */
-    if (drv == &bdrv_vvfat)
+    /* no need to test disk image format if the filename told us */
+    if (drv != NULL)
          return drv;

find_protocol doesn't tell you the image format of a file, it tells you 
a protocol through which you should obtain the image. And the image you 
get could be a qcow image then. I think the reason why they are using 
bdrv functions for all file accesses is that e.g. the qcow driver could 
use the protocol driver then (if there was any protocol driver...)

Currently xend won't let you specify a filename with a protocol 
specifier anyway, so removing the whole thing is certainly an option.

Kevin

  reply	other threads:[~2008-05-15 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  9:50 VMX status report. Xen: #17630 & Xen0: #540 -- blocked Li, Haicheng
2008-05-14 10:44 ` Ian Jackson
2008-05-15  7:40   ` Li, Haicheng
2008-05-15  8:30     ` Xu, Dongxiao
2008-05-15  9:00       ` Kevin Wolf
2008-05-15  9:31         ` Xu, Dongxiao
2008-05-15  9:50           ` Kevin Wolf
2008-05-15 11:07             ` Ian Jackson
2008-05-15 11:54               ` Kevin Wolf [this message]
2008-05-15 13:07                 ` Ian Jackson
2008-05-15 13:53                   ` Kevin Wolf
2008-05-16  1:38               ` Xu, Dongxiao
2008-05-16  9:14                 ` Ian Jackson

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=482C2489.6050709@suse.de \
    --to=kwolf@suse.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dongxiao.xu@intel.com \
    --cc=haicheng.li@intel.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.