linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Smart <james.smart@broadcom.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	dick kennedy <dick.kennedy@broadcom.com>
Subject: Re: linux-next: Tree for Jul 7 (scsi/lpfc/lpfc_init.c)
Date: Tue, 7 Jul 2020 11:12:00 -0700	[thread overview]
Message-ID: <7ae1c7e3-ce8d-836b-1ae7-d4d00bd8f95c@broadcom.com> (raw)
In-Reply-To: <2f85f3c4-a58b-f225-a533-86e209a4651c@infradead.org>

On 7/7/2020 10:09 AM, Randy Dunlap wrote:
> On 7/7/20 1:08 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20200706:
>>
> on i386:
>
> when CONFIG_ACPI is not set/enabled:
>
>
> ../drivers/scsi/lpfc/lpfc_init.c:1265:15: error: implicit declaration of function 'get_cpu_idle_time'; did you mean 'get_cpu_device'? [-Werror=implicit-function-declaration]
>
>
> The cpufreq people want justification for using
> get_cpu_idle_time().  Please see
> https://lore.kernel.org/linux-scsi/20200707030943.xkocccy6qy2c3hrx@vireshk-i7/
>
>
>

The driver is using cpu utilization in order to choose between softirq 
or work queues in handling an interrupt. Less-utilized, softirq is used. 
higher utilized, work queue is used.  The utilization is checked 
periodically via a heartbeat.

-- james


  reply	other threads:[~2020-07-07 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200707180800.549b561b@canb.auug.org.au>
2020-07-07 17:09 ` linux-next: Tree for Jul 7 (scsi/lpfc/lpfc_init.c) Randy Dunlap
2020-07-07 18:12   ` James Smart [this message]
2020-07-08  2:46     ` Viresh Kumar

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=7ae1c7e3-ce8d-836b-1ae7-d4d00bd8f95c@broadcom.com \
    --to=james.smart@broadcom.com \
    --cc=dick.kennedy@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).