On Thu, 4 Jan 2018, Johannes Berg wrote:
> On Thu, 2017-12-21 at 11:42 +0100, Anna-Maria Gleixner wrote:
> > From: Thomas Gleixner <t...@linutronix.de>
> >
> > Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
>
> I've pointed out before that this
he
> "next" pointer. Oh well. Nobody cares, except for the list entry
> debugging code, which isn't run on the hlist cases.
>
> Adding Thomas Gleixner to the cc. It should not be possible to delete
> the same timer twice.
Right, it shouldn't.
Fengguang, can you please en
On Mon, 23 Oct 2017, Johannes Berg wrote:
> On Mon, 2017-10-23 at 12:23 +0200, Thomas Gleixner wrote:
> > On Mon, 23 Oct 2017, Johannes Berg wrote:
> >
> > > On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote:
> > > > From: Thomas Gleixner <t...
On Mon, 23 Oct 2017, Johannes Berg wrote:
> On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote:
> > From: Thomas Gleixner <t...@linutronix.de>
> >
> > Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
> > callback in softirq context a
On Thu, 5 Oct 2017, Daniel Drake wrote:
> On Mon, Oct 2, 2017 at 10:38 PM, Thomas Gleixner <t...@linutronix.de> wrote:
> > What's wrong with just using the legacy INTx emulation if you cannot
> > allocate 4 MSI vectors?
>
> The Legacy interrupt simply doesn't work for
On Tue, 3 Oct 2017, Bjorn Helgaas wrote:
> On Tue, Oct 03, 2017 at 11:07:58PM +0200, Thomas Gleixner wrote:
> > On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > > On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > > > On Mon, 2 Oct 2017, Daniel Drake wrote:
> > >
On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > On Mon, 2 Oct 2017, Daniel Drake wrote:
> > 2) The affinity setting of straight MSI interrupts (w/o remapping) on x86
> > requires to make the affinity change from
On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> On Mon, 2 Oct 2017, Daniel Drake wrote:
> 2) The affinity setting of straight MSI interrupts (w/o remapping) on x86
> requires to make the affinity change from the interrupt context of the
> current active vector in order
Daniel,
On Mon, 2 Oct 2017, Daniel Drake wrote:
> On Wed, Sep 27, 2017 at 11:28 PM, Thomas Gleixner <t...@linutronix.de> wrote:
> On another system, I have multiple devices using IR-PCI-MSI according
> to /proc/interrupts, and lspci shows that a MSI Message Data value 0
> is use
On Mon, 25 Sep 2017, Daniel Drake wrote:
Please send x86 related patches to LKML as documented in MAINTAINERS. That
patch is mainly x86 and not PCI.
> ath9k hardware claims to support up to 4 MSI vectors, and when run in
> that configuration, it would be allowed to modify the lower bits of the
>
On Tue, 5 Sep 2017, Sebastian Andrzej Siewior wrote:
> On 2017-09-05 09:12:40 [+0200], Thomas Gleixner wrote:
> > Sorry, no. That bisect is completely bogus. The commit in question merily
> > replaces the unsupported clockid with a valid one.
>
> The bisect is correct.
On Tue, 5 Sep 2017, Johannes Berg wrote:
> On Thu, 2017-08-31 at 12:23 +, Anna-Maria Gleixner wrote:
> > From: Thomas Gleixner <t...@linutronix.de>
> >
> > Switch the timer to CLOCK_MONOTONIC_SOFT, which executed the timer
> > callback in softirq conte
On Fri, 17 Feb 2017, Marc Zyngier wrote:
> On 17/02/17 09:28, Thomas Gleixner wrote:
> > On Fri, 17 Feb 2017, kernel test robot wrote:
> >
> >> Hi Marc,
> >>
> >> We find this oops in linux-4.4.y. The gcc-6 compiled mainline kernel is
> >> f
On Fri, 17 Feb 2017, kernel test robot wrote:
> Hi Marc,
>
> We find this oops in linux-4.4.y. The gcc-6 compiled mainline kernel is fine.
>
> commit 4fc2942b6e2de2efc8a9d3784d4b0d3543149613
> hrtimer: Catch illegal clockids
And that commit is doing what the subject line says. Catch
14 matches
Mail list logo
