From: "Liu, Jinsong" <jinsong.liu@intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad@kernel.org>
Subject: RE: [PATCH V3 1/2] Xen stub driver for memory hotplug
Date: Thu, 24 Jan 2013 13:56:56 +0000 [thread overview]
Message-ID: <DE8DF0795D48FD4CA783C40EC82923353DC766@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20130123195455.GA18022@phenom.dumpdata.com>
>> +#include <linux/kernel.h>
>> +#include <linux/init.h>
>> +#include <linux/export.h>
>> +#include <linux/types.h>
>> +#include <linux/acpi.h>
>> +#include <acpi/acpi_drivers.h>
>> +#include <xen/acpi.h>
>> +
>> +/*--------------------------------------------
>> + stub driver for Xen memory hotplug
>> +--------------------------------------------*/
>> +
>> +#ifdef CONFIG_ACPI
>> +
>> +static const struct acpi_device_id memory_device_ids[] = {
>> + {ACPI_MEMORY_DEVICE_HID, 0},
>> + {"", 0},
>> +};
>> +
>> +struct acpi_driver xen_stub_memory_device_driver = {
>> + /* same name as native memory driver to block native loaded */
>> + .name = "acpi_memhotplug", + .class = ACPI_MEMORY_DEVICE_CLASS,
>> + .ids = memory_device_ids,
>> +};
>> +EXPORT_SYMBOL_GPL(xen_stub_memory_device_driver);
>
> Instead of having this, could you have a function that would
> unregister this if required.
>
> xen_stub_memory_device_uninit(void)
>
> which would unregister the above mentioned structure?
>
Yup, updated by EXPORT_SYMBOL_GPL 2 funcs:
xen_stub_memory_device_init()
xen_stub_memory_device_exit()
Thanks,
Jinsong
prev parent reply other threads:[~2013-01-24 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 6:09 Liu, Jinsong
2013-01-23 19:54 ` Konrad Rzeszutek Wilk
2013-01-24 13:56 ` Liu, Jinsong [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=DE8DF0795D48FD4CA783C40EC82923353DC766@SHSMSX101.ccr.corp.intel.com \
--to=jinsong.liu@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®