mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Prarit Bhargava <prarit@redhat.com>,
	Ming Lei <ming.lei@canonical.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	x86@kernel.org, amd64-microcode@amd64.org
Subject: [PATCH 0/2] Add request_firmware_direct() for microcode loader
Date: Tue,  5 Nov 2013 12:57:04 +0100	[thread overview]
Message-ID: <1383652626-30437-1-git-send-email-tiwai@suse.de> (raw)

Hi,

this is a patch series to introduce request_firmware_direct() helper
for avoiding the lengthy udev issue on microcode loader.
The original problem was stated in Prarit's post:
   https://lkml.org/lkml/2013/10/28/221

In short, microcode loader probes non-existing firmware files (which
are cases with every new chip), and each probe takes 60 seconds,
resulting in too long time until completed.

This solution is simply avoiding the udev fallback in
request_firmware() explicitly for drivers like microcode.

 [PATCH 1/2] firmware: Introduce request_firmware_direct()
 [PATCH 2/2] microcode: Use request_firmware_direct()

Of course, this doesn't mean to throw away further optimizations like
Prarit's patch.  It can be implemented in parallel with this.


thanks,

Takashi

             reply	other threads:[~2013-11-05 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 11:57 Takashi Iwai [this message]
2013-11-05 11:57 ` [PATCH 1/2] firmware: Introduce request_firmware_direct() Takashi Iwai
2013-11-11  7:44   ` Ming Lei
2013-11-11 15:10     ` Takashi Iwai
2013-11-05 11:57 ` [PATCH 2/2] microcode: Use request_firmware_direct() Takashi Iwai

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=1383652626-30437-1-git-send-email-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=amd64-microcode@amd64.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=prarit@redhat.com \
    --cc=x86@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®