From: Chris Lalancette <clalance@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [PATCH 3/4]: Extend blktap userland busid to 32-bits
Date: Mon, 23 Jun 2008 20:29:07 +0200 [thread overview]
Message-ID: <485FEB73.5080809@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
(please ignore my [PATCH 3/5]; this is the same thing with a proper subject)
This patch just extends the busid in the userland tools to 32-bits to match the
extension we made in the last patch in the kernel.
Signed-off-by: Chris Lalancette <clalance@redhat.com>
[-- Attachment #2: xen-unstable-greater-16-vbd-tools-blktap.patch --]
[-- Type: text/x-patch, Size: 866 bytes --]
diff -r dedfadeadf86 tools/blktap/drivers/blktapctrl.c
--- a/tools/blktap/drivers/blktapctrl.c Fri Jun 20 18:42:45 2008 +0100
+++ b/tools/blktap/drivers/blktapctrl.c Mon Jun 23 17:48:13 2008 +0200
@@ -127,7 +127,7 @@ static int get_new_dev(int *major, int *
char *devname;
tr.domid = blkif->domid;
- tr.busid = (unsigned short)blkif->be_id;
+ tr.busid = blkif->be_id;
ret = ioctl(ctlfd, BLKTAP_IOCTL_NEWINTF, tr );
if ( (ret <= 0)||(ret > MAX_TAP_DEV) ) {
diff -r dedfadeadf86 tools/blktap/lib/blktaplib.h
--- a/tools/blktap/lib/blktaplib.h Fri Jun 20 18:42:45 2008 +0100
+++ b/tools/blktap/lib/blktaplib.h Mon Jun 23 17:48:13 2008 +0200
@@ -161,7 +161,7 @@ typedef struct tapdev_info {
typedef struct domid_translate {
unsigned short domid;
- unsigned short busid;
+ uint32_t busid;
} domid_translate_t ;
typedef struct image {
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2008-06-23 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=485FEB73.5080809@redhat.com \
--to=clalance@redhat.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.