From: Peter Zijlstra <peterz@infradead.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com, mingo@redhat.com,
Douglas_Warzecha@dell.com, pali.rohar@gmail.com,
jdelvare@suse.com, linux@roeck-us.net, tglx@linutronix.de,
hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH 0/6] Support calling functions on dedicated physical cpu
Date: Fri, 11 Mar 2016 14:19:17 +0100 [thread overview]
Message-ID: <20160311131917.GD6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160311131504.109cb244@lxorguk.ukuu.org.uk>
On Fri, Mar 11, 2016 at 01:15:04PM +0000, One Thousand Gnomes wrote:
> On Fri, 11 Mar 2016 13:25:14 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Fri, Mar 11, 2016 at 12:59:28PM +0100, Juergen Gross wrote:
> > > Some hardware (e.g. Dell Studio laptops) require special functions to
> > > be called on physical cpu 0 in order to avoid occasional hangs. When
> > > running as dom0 under Xen this could be achieved only via special boot
> > > parameters (vcpu pinning) limiting the hypervisor in it's scheduling
> > > decisions.
> >
> > So instead of telling Dell to get their act together and fix their damn
> > firmware, we're going to add the most horrid gunk to the kernel? How
> > does that make sense?
>
> It's been normal forever. The convention with a lot of older BIOS crap
> was always that it should be called on the boot CPU (APM. PnPBIOS etc).
>
> It's a stretch pre-EFI to even call it a "bug"
Yeah, I knew about the APM/PnP muck, but I was under the impression this
was about new hardware.
next prev parent reply other threads:[~2016-03-11 13:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:59 [PATCH 0/6] Support calling functions on dedicated physical cpu Juergen Gross
2016-03-11 11:59 ` [PATCH 1/6] xen: sync xen header Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 11:59 ` [PATCH 2/6] sched: add function to execute a function synchronously on a physical cpu Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 12:19 ` Peter Zijlstra
2016-03-11 12:42 ` Peter Zijlstra
2016-03-11 12:42 ` Peter Zijlstra
2016-03-11 12:48 ` Juergen Gross
2016-03-11 12:48 ` Juergen Gross
2016-03-11 12:57 ` Peter Zijlstra
2016-03-11 12:57 ` Peter Zijlstra
2016-03-11 13:07 ` Juergen Gross
2016-03-11 13:07 ` Juergen Gross
2016-03-11 12:43 ` Juergen Gross
2016-03-11 12:43 ` Juergen Gross
2016-03-11 12:45 ` Peter Zijlstra
2016-03-11 12:45 ` Peter Zijlstra
2016-03-11 12:19 ` Peter Zijlstra
2016-03-11 11:59 ` [PATCH 3/6] dcdbas: make use of call_sync_on_phys_cpu() Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 11:59 ` [PATCH 4/6] hwmon: use call_sync_on_phys_cpu() for dell-smm i8k Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 11:59 ` [PATCH 5/6] virt, sched: add cpu pinning to call_sync_on_phys_cpu() Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 11:59 ` [PATCH 6/6] xen: add xen_pin_vcpu() to support calling functions on a dedicated pcpu Juergen Gross
2016-03-11 11:59 ` Juergen Gross
2016-03-11 12:25 ` [PATCH 0/6] Support calling functions on dedicated physical cpu Peter Zijlstra
2016-03-11 12:28 ` Pali Rohár
2016-03-11 12:28 ` Pali Rohár
2016-03-11 13:15 ` One Thousand Gnomes
2016-03-11 13:15 ` One Thousand Gnomes
2016-03-11 13:19 ` Peter Zijlstra [this message]
2016-03-11 13:19 ` Peter Zijlstra
2016-03-11 12:25 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2016-03-11 11:59 Juergen Gross
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=20160311131917.GD6344@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Douglas_Warzecha@dell.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=pali.rohar@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.