From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
stefanha@gmail.com, kwolf@redhat.com, prerna@linux.vnet.ibm.com
Subject: Re: [PATCH, RFC] virtio_blk: add cache control support
Date: Fri, 25 Mar 2011 15:38:51 +1030 [thread overview]
Message-ID: <8762r7lrbw.fsf@rustcorp.com.au> (raw)
In-Reply-To: <4D8B14BD.2060602@de.ibm.com>
On Thu, 24 Mar 2011 10:54:05 +0100, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Am 24.03.2011 04:05, schrieb Anthony Liguori:
> >> ie. lguest and S/390 don't trap writes to config space.
> >>
> >> Or perhaps they should? But we should be explicit about needing it...
> > I don't think we ever operated on the assumption that config space writes would trap.
> >
> > I don't think adding it is the right thing either because you can do byte access to the config space which makes atomicity difficult.
>
> There is the additional problem, that s390 has no MMIO and,therefore,
> there is no real HW support for trapping writes to an area. You can
> use page faults, or read-only faults on newer systems, but this is
> expensive. In addition, page faults only deliver the page frame, but
> not the offset within a page.
That's not *really* a problem, since you have control over the
config_set operation and could do whatever you wanted.
But I wanted to make sure we're all on the same page: you *can't* rely
on the host knowing immediately what you write to the config space. If
you want that, an actual queued request is necessary...
Thanks,
Rusty.
prev parent reply other threads:[~2011-03-25 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110315141049.GA30627@lst.de>
2011-03-15 14:16 ` [PATCH, RFC] virtio_blk: add cache control support Christoph Hellwig
2011-03-16 4:09 ` Rusty Russell
2011-03-16 14:09 ` Christoph Hellwig
2011-03-17 5:06 ` Rusty Russell
2011-03-17 14:21 ` [Qemu-devel] " Christoph Hellwig
2011-03-24 0:11 ` Rusty Russell
2011-03-24 3:11 ` Anthony Liguori
2011-03-24 3:05 ` Anthony Liguori
2011-03-24 9:54 ` Christian Borntraeger
2011-03-25 5:08 ` Rusty Russell [this message]
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=8762r7lrbw.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox