From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.osdl.org
Subject: Re: INDIRECT and NEXT
Date: Fri, 23 Oct 2009 14:01:23 +1030 [thread overview]
Message-ID: <200910231401.24419.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20091022093745.GA27765@redhat.com>
On Thu, 22 Oct 2009 08:07:45 pm Michael S. Tsirkin wrote:
> Imagine an indirect entry where NEXT bit is also set.
Hmm, so it's not obvious whether the kvm userspace code handles it
correctly either.
Want to hack something up to use NEXT + INDIRECT, then we can actually test
it? If it doesn't work, this will have to be a new feature bit.
Also, we have a limitation that you can't have more descriptors than the ring
size, even with indirect, due to overzealous checks...
Thanks,
Rusty.
next prev parent reply other threads:[~2009-10-23 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091004143734.GB17578@redhat.com>
2009-10-19 2:34 ` INDIRECT and NEXT Rusty Russell
2009-10-22 9:37 ` Michael S. Tsirkin
2009-10-23 3:31 ` Rusty Russell [this message]
2009-10-23 6:36 ` Michael S. Tsirkin
2009-10-23 9:20 ` Rusty Russell
2009-10-23 9:30 ` Michael S. Tsirkin
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=200910231401.24419.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=mst@redhat.com \
--cc=virtualization@lists.osdl.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).