From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] linux: Allow actually using CONFIG_XEN_BLKDEV_TAP=m
Date: Thu, 25 Oct 2007 10:17:12 +0100 [thread overview]
Message-ID: <47207B38.76E4.0078.0@novell.com> (raw)
Again, this got broken. It would be really nice if regression testing
included building as a module everything that can be configured as
such...
As usual, written and tested against 2.6.23 and made apply against
2.6.18 without further testing.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-10-15/arch/i386/mm/hypervisor.c
===================================================================
--- head-2007-10-15.orig/arch/i386/mm/hypervisor.c 2007-10-19 17:17:09.000000000 +0200
+++ head-2007-10-15/arch/i386/mm/hypervisor.c 2007-10-19 17:17:59.000000000 +0200
@@ -56,6 +56,7 @@ void xen_l1_entry_update(pte_t *ptr, pte
u.val = __pte_val(val);
BUG_ON(HYPERVISOR_mmu_update(&u, 1, NULL, DOMID_SELF) < 0);
}
+EXPORT_SYMBOL_GPL(xen_l1_entry_update);
void xen_l2_entry_update(pmd_t *ptr, pmd_t val)
{
Index: head-2007-10-15/drivers/xen/blktap/blktap.c
===================================================================
--- head-2007-10-15.orig/drivers/xen/blktap/blktap.c 2007-10-19 17:17:15.000000000 +0200
+++ head-2007-10-15/drivers/xen/blktap/blktap.c 2007-06-22 09:21:11.000000000 +0200
@@ -116,13 +116,7 @@ typedef struct tap_blkif {
static struct tap_blkif *tapfds[MAX_TAP_DEV];
static int blktap_next_minor;
-static int __init set_blkif_reqs(char *str)
-{
- get_option(&str, &blkif_reqs);
- return 1;
-}
-__setup("blkif_reqs=", set_blkif_reqs);
-
+module_param(blkif_reqs, int, 0);
/* Run-time switchable: /sys/module/blktap/parameters/ */
static unsigned int log_stats = 0;
static unsigned int debug_lvl = 0;
next reply other threads:[~2007-10-25 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 9:17 Jan Beulich [this message]
2007-10-25 9:23 ` [PATCH] linux: Allow actually using CONFIG_XEN_BLKDEV_TAP=m Steve Kemp
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=47207B38.76E4.0078.0@novell.com \
--to=jbeulich@novell.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.