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: Mon, 19 Oct 2009 13:04:20 +1030 [thread overview]
Message-ID: <200910191304.20748.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20091004143734.GB17578@redhat.com>
On Mon, 5 Oct 2009 01:07:34 am Michael S. Tsirkin wrote:
> Hi!
> I note that chaining INDIRECT descriptors with NEXT
> currently is broken in lguest, because current
> ring index gets overwritten.
I agree this should be fixed, but not quite sure what you're referring to.
I could force indirect and reproduce it, but I figure asking you for details
would be more efficient :)
Thanks!
Rusty.
next parent reply other threads:[~2009-10-19 2:34 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 ` Rusty Russell [this message]
2009-10-22 9:37 ` INDIRECT and NEXT Michael S. Tsirkin
2009-10-23 3:31 ` Rusty Russell
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=200910191304.20748.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).