From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [Xen-devel] [PATCH] xen-pciback: Add MODULE_ALIAS for pciback.
Date: Wed, 26 Nov 2014 12:18:48 -0500 [thread overview]
Message-ID: <201411261718.sAQHIsgd027807@aserz7022.oracle.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1557 bytes --]
On Nov 26, 2014 11:39 AM, "Luis R. Rodriguez" <mcgrof@do-not-panic.com> wrote:
>
> On Wed, Aug 20, 2014 at 1:26 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
> > On Wed, 2014-08-20 at 13:20 -0400, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Aug 20, 2014 at 06:18:52PM +0100, Ian Campbell wrote:
> >> > On Wed, 2014-08-20 at 12:40 -0400, Konrad Rzeszutek Wilk wrote:
> >> > > The rest of the Xen device drivers use an module alias
> >> > > to load devices when they shop up in XenBus.
> >> >
> >> > "show".
> >> > >
> >> > >Â MODULE_LICENSE("Dual BSD/GPL");
> >> > >Â MODULE_ALIAS("xen-backend:pci");
> >> > > +MODULE_ALIAS("xen:pci");
> >> >
> >> > Isn't that xen-backend:pci already the right thing for a backend device?
> >> > xen: is for frontends, I thought.
> >>
> >> Oh, you are right. Cool! Thanks!
> >
> > The patch turned out to be even more trivial than expected ;-)
>
> Is this what we expected to be pending work for the item "device
> hotplug (MODULE_ALIAS)" on the upstream TODO list?
>
> http://wiki.xenproject.org/wiki/XenParavirtOps#Upstream_delta_details
>
> This was simply to just auto load that driver when needed right?
>
Right which it does now.
> Also as for actual PCI device hotplug support:
>
> http://wiki.xen.org/wiki/Xen_PCI_Passthrough#Hotplug
>
> I don't think we need a delta for that do we?
Nope. This one is all done.
>
> Luis
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2014-11-26 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 17:18 Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 16:40 [PATCH] Add MODULE_ALIAS for Xen pciback. (v1) Konrad Rzeszutek Wilk
2014-08-20 16:40 ` [PATCH] xen-pciback: Add MODULE_ALIAS for pciback Konrad Rzeszutek Wilk
2014-08-20 17:18 ` [Xen-devel] " Ian Campbell
2014-08-20 17:20 ` Konrad Rzeszutek Wilk
2014-08-20 17:26 ` Ian Campbell
2014-11-26 16:39 ` Luis R. Rodriguez
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=201411261718.sAQHIsgd027807@aserz7022.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®