virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "KONRAD Frédéric" <fred.konrad@greensocs.com>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: what should a virtio-mmio transport without a backend look like?
Date: Fri, 21 Jun 2013 14:01:19 -0400	[thread overview]
Message-ID: <51C494EF.4060509@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA-iBduDCbwHYYe7BhAXoBx2A5EgZ6_251B3vMuODewxvQ@mail.gmail.com>

Hi Peter,

On 06/21/2013 01:01 PM, Peter Maydell wrote:
> On 21 June 2013 17:47, Pawel Moll <pawel.moll@arm.com> wrote:
>> On Fri, 2013-06-21 at 17:41 +0100, Peter Maydell wrote:
>>> As it happens, if you use the command line to specify
>>> a virtio device it doesn't make the same complaint about
>>> bad magic number as if you specify it via dtb, but that
>>> should probably be fixed in the kernel :-)
>>
>> I don't really see how this would be possible - the "complaining code"
>> is just a normal platform device probe function.
> 
> Sorry, you're correct and I misremembered. I just retested
> with specifying via command line and it behaves the same
> way as via dtb.

I was going to say something. I see that complaint all the time.

Anyhow, I just did a quick experiment with 0-size block devices, and they seem
to work for me, although trying to mount the device yields the confusing
message, "mount: mounting /dev/vda on mount failed: Invalid argument".

Regards,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  reply	other threads:[~2013-06-21 18:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFEAcA9qCUQLZho8wJvewYJ0AEhDBc37_LpZWs8XBV1U7RVZgA@mail.gmail.com>
2013-06-20 11:08 ` what should a virtio-mmio transport without a backend look like? Pawel Moll
2013-06-20 12:58   ` Christopher Covington
2013-06-21 15:23     ` Peter Maydell
2013-06-21 16:02       ` Christopher Covington
2013-06-21 16:41         ` Peter Maydell
2013-06-21 16:47           ` Pawel Moll
2013-06-21 17:01             ` Peter Maydell
2013-06-21 18:01               ` Christopher Covington [this message]
2013-06-21 18:28                 ` Peter Maydell
2013-06-21 18:45                   ` Christopher Covington
2013-06-22 10:51                     ` Peter Maydell
2013-06-24 12:26                       ` Christopher Covington
2013-06-24 12:57                         ` Peter Maydell
2013-06-21 20:13                   ` Paolo Bonzini
2013-07-01  0:07   ` Rusty Russell

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=51C494EF.4060509@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=fred.konrad@greensocs.com \
    --cc=pawel.moll@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=virtualization@lists.linux-foundation.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).