mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/5, resend] PCI: adjust quirk handler section annotations
Date: Wed, 09 May 2012 17:02:28 +0100	[thread overview]
Message-ID: <4FAAB134020000780008294F@nat28.tlf.novell.com> (raw)
In-Reply-To: <CAErSpo68N5JYv_SX7Qzu4e0Z=x_g1U+FPaA-ux_W_zoB6iW+pw@mail.gmail.com>

>>> On 09.05.12 at 17:54, Bjorn Helgaas <bhelgaas@google.com> wrote:
> On Wed, May 9, 2012 at 1:43 AM, Jan Beulich <JBeulich@suse.com> wrote:
>> This is in preparation to adjust modpost to check section mismatches
>> on most of the .pci_fixup* sections:
>>
>> .pci_fixup_final is only used from .init.text, and hence can (along
>> with the respective handler functions) reside in .init.*.
> 
> pci_apply_final_quirks() is currently __init, so this probably
> wouldn't break anything.   But the fact that it's all __init means
> that pci_fixup_final quirks are only run for devices present at boot,
> and they don't apply to hot-added devices.  That seems like a bug to
> me.
> 
>> Several other .pci_fixup_* sections are needed only during boot and
>> suspend/resume, and can therefore be moved into .init.* if
>> !CONFIG_PM.
> 
> My inclination is that all PCI fixups should work the same for
> hot-added devices as for those present at boot, which would suggest
> that we should always use __devinit, not __init.  If I'm missing
> something, please educate me :)

That's certainly possible - I simply based the patch on what is there
currently.

Jan


  reply	other threads:[~2012-05-09 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  8:43 Jan Beulich
2012-05-09 15:54 ` Bjorn Helgaas
2012-05-09 16:02   ` Jan Beulich [this message]
2012-05-09 16:08     ` Bjorn Helgaas
2012-05-09 16:56       ` Jan Beulich

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=4FAAB134020000780008294F@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=bhelgaas@google.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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®