From: Christoph Egger <Christoph.Egger@amd.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] block/raw-posix: use a character device if a block device is given
Date: Wed, 25 May 2011 14:19:46 +0200 [thread overview]
Message-ID: <4DDCF3E2.5080900@amd.com> (raw)
In-Reply-To: <4DDCDD55.6050602@redhat.com>
On 05/25/11 12:43, Kevin Wolf wrote:
> Am 24.05.2011 11:30, schrieb Christoph Egger:
>>
>> On NetBSD a userland process is better with the character device
>> interface. In addition, a block device can't be opened twice; if a Xen
>> backend opens it, qemu can't and vice-versa.
>
> If you provide a Signed-off-by, I think this patch is ready to be committed.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> Kevin
>
>>
>> diff --git a/block/raw-posix.c b/block/raw-posix.c
>> index 6b72470..64dceb1 100644
>> --- a/block/raw-posix.c
>> +++ b/block/raw-posix.c
>> @@ -136,12 +143,55 @@ static int64_t raw_getlength(BlockDriverState *bs);
>> static int cdrom_reopen(BlockDriverState *bs);
>> #endif
>>
>> +#if defined(__NetBSD__)
>> +static int raw_normalize_devicepath(const char **filename)
>> +{
>> + static char namebuf[PATH_MAX];
>> + const char *dp, *fname;
>> + struct stat sb;
>> +
>> + fname = *filename;
>> + dp = strrchr(fname, '/');
>> + if (lstat(fname,&sb)< 0) {
>> + fprintf(stderr, "%s: stat failed: %s\n",
>> + fname, strerror(errno));
>> + return -errno;
>> + }
>> +
>> + if (!S_ISBLK(sb.st_mode)) {
>> + return 0;
>> + }
>> +
>> + if (dp == NULL) {
>> + snprintf(namebuf, PATH_MAX, "r%s", fname);
>> + } else {
>> + snprintf(namebuf, PATH_MAX, "%.*s/r%s",
>> + (int)(dp - fname), fname, dp + 1);
>> + }
>> + fprintf(stderr, "%s is a block device", fname);
>> + *filename = namebuf;
>> + fprintf(stderr, ", using %s\n", *filename);
>> +
>> + return 0;
>> +}
>> +#else
>> +static int raw_normalize_devicepath(const char **filename)
>> +{
>> + return 0;
>> +}
>> +#endif
>> +
>> static int raw_open_common(BlockDriverState *bs, const char *filename,
>> int bdrv_flags, int open_flags)
>> {
>> BDRVRawState *s = bs->opaque;
>> int fd, ret;
>>
>> + ret = raw_normalize_devicepath(&filename);
>> + if (ret != 0) {
>> + return ret;
>> + }
>> +
>> s->open_flags = open_flags | O_BINARY;
>> s->open_flags&= ~O_ACCMODE;
>> if (bdrv_flags& BDRV_O_RDWR) {
>>
>>
>
>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-05-25 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 9:30 [Qemu-devel] [PATCH] block/raw-posix: use a character device if a block device is given Christoph Egger
2011-05-25 10:43 ` Kevin Wolf
2011-05-25 12:19 ` Christoph Egger [this message]
2011-05-25 13:01 ` Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 12:34 Christoph Egger
2011-05-23 13:42 ` Christoph Hellwig
2011-05-23 13:49 ` Christoph Egger
2011-05-23 14:11 ` Kevin Wolf
2011-05-24 8:36 ` Christoph Egger
2011-05-24 9:10 ` Kevin Wolf
2011-05-24 9:24 ` Christoph Egger
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=4DDCF3E2.5080900@amd.com \
--to=christoph.egger@amd.com \
--cc=kwolf@redhat.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).