From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: C Anthony Risinger <anthony@xtfx.me>
Subject: Re: [Qemu-devel] VirtIO 9p mount_tag (bogus?) limit of 32 bytes
Date: Thu, 16 Feb 2012 20:54:17 +0000 [thread overview]
Message-ID: <201202162054.18209.paul@codesourcery.com> (raw)
In-Reply-To: <CAGAVQTHimKBTkLHMFcwSeNYJqV=y0dvor-D6s+M8UHTmmzHAxQ@mail.gmail.com>
> i see an error message has been added, which is great (i killed a
> couple hours of $%!@ until i noticed the truncated length was *exactly
> 32* bytes; silent truncation), but it would really be great if this
> restriction could be lifted, or at least mitigated by expanding the
> field some.
>
> is config space that precious?
Yes.
> what constrains it (personal curiosity :-)?
Virtio PCI devices map the config space directly onto an ISA IO port range,
along with the virtio control structure. On most systems (in particular
anything PC based) this is a 16-bit address space. i.e. you have
substantually less than 64k of virtio config space for the whole machine, and
potentially only a couple of kbytes for a given PCI bus.
Paul
next prev parent reply other threads:[~2012-02-16 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:20 [Qemu-devel] VirtIO 9p mount_tag (bogus?) limit of 32 bytes C Anthony Risinger
2012-02-16 20:54 ` Paul Brook [this message]
2012-02-18 17:38 ` Aneesh Kumar K.V
2012-02-22 3:58 ` C Anthony Risinger
2012-02-23 18:08 ` Aneesh Kumar K.V
2012-03-07 16:29 ` M. Mohan Kumar
-- strict thread matches above, loose matches on Subject: below --
2011-09-22 17:42 Daniel P. Berrange
2011-09-28 11:52 ` Harsh Bora
2011-09-28 15:18 ` Daniel P. Berrange
2011-09-29 15:22 ` Aneesh Kumar K.V
2011-09-29 15:45 ` Daniel P. Berrange
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=201202162054.18209.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=anthony@xtfx.me \
--cc=qemu-devel@nongnu.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 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.