From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Chris Wilson <chris@chris-wilson.co.uk>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Chen Fan <chen.fan.fnst@cn.fujitsu.com>,
Alexander Potapenko <glider@google.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] softirq: Reserve a bit in tasklet.state for the user
Date: Mon, 23 Jan 2017 17:10:23 +0100 [thread overview]
Message-ID: <20170123161023.GI6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1701231657380.3836@nanos>
On Mon, Jan 23, 2017 at 04:59:32PM +0100, Thomas Gleixner wrote:
> On Mon, 23 Jan 2017, Jens Axboe wrote:
>
> > On 01/23/2017 08:33 AM, Chris Wilson wrote:
> > > Allow the user to communicate with the tasklet through the atomic state
> > > field by assigning a bit for their use. This can be used, for example,
> > > to differentiate between a tasklet called following an irq or from
> > > process context, where some hardware state may only be valid after the
> > > irq.
Egads, this sounds like a horrible hack. What does 'after and irq' even
mean?
prev parent reply other threads:[~2017-01-23 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 15:33 Chris Wilson
2017-01-23 15:44 ` Jens Axboe
2017-01-23 15:57 ` [PATCH] drm/i915: Only run execlist context-switch handler after an interrupt Chris Wilson
2017-01-23 15:59 ` [PATCH] softirq: Reserve a bit in tasklet.state for the user Thomas Gleixner
2017-01-23 16:10 ` Peter Zijlstra [this message]
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=20170123161023.GI6500@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=chris@chris-wilson.co.uk \
--cc=glider@google.com \
--cc=hare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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®