From: Jamie Lokier <jamie@shareable.org>
To: Catalin BOIE <util@deuroconsult.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: idt change in a running kernel? what locking?
Date: Mon, 6 Oct 2003 18:07:07 +0100 [thread overview]
Message-ID: <20031006170707.GA559@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0310060810440.26313@hosting.rdsbv.ro>
Catalin BOIE wrote:
> What I realy want is to reload idt on every cpu.
> So, probably on_each_cpu is the way to go, right?
Yes. If you also want to synchronise the changes, so that all CPUs
appear to change idt at the same instant, you'll need some extra
locking.
-- Jamie
next prev parent reply other threads:[~2003-10-06 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 5:52 idt change in a running kernel? what locking? Catalin BOIE
2003-10-03 6:34 ` Jamie Lokier
2003-10-03 6:52 ` Catalin BOIE
2003-10-03 17:02 ` Jamie Lokier
2003-10-06 5:12 ` Catalin BOIE
2003-10-06 17:07 ` Jamie Lokier [this message]
2003-10-07 4:35 ` Catalin BOIE
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=20031006170707.GA559@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util@deuroconsult.ro \
/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