From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH, RFC] Configuration device: add write channel, mark pages RO
Date: Sun, 7 Sep 2008 21:56:56 +0300 [thread overview]
Message-ID: <f43fc5580809071156k37f4c5edw98bba0ce76ea3430@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi,
The first patch extend the configuration device with a guest write
capability. A callback is invoked when the buffer is full.
It's a bit odd to get completely different behavior when doing I/O to
the same port just because of the word size used in the IO. I'd rather
have two ports, one for control write or status read and another for
data read/write. Is two ports too much to ask on a PC?
The second patch uses the first one to add a new key for marking guest
pages read only. This patch was inspired due to discussion I saw on
KernelTrap:
http://kerneltrap.org/mailarchive/linux-kernel/2008/9/4/3191234
[-- Attachment #2: fw_cfg_write_channel.diff --]
[-- Type: plain/text, Size: 5120 bytes --]
[-- Attachment #3: fw_cfg_ro_page.diff --]
[-- Type: plain/text, Size: 2818 bytes --]
next reply other threads:[~2008-09-07 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 18:56 Blue Swirl [this message]
2008-09-08 6:05 ` [Qemu-devel] [PATCH, RFC] Configuration device: add write channel, mark pages RO Gleb Natapov
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=f43fc5580809071156k37f4c5edw98bba0ce76ea3430@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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 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).