From: ebiederm@xmission.com (Eric W. Biederman)
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH] x86: Don't write io_apic ID if it is not changed
Date: Sun, 15 Aug 2010 08:55:00 -0700 [thread overview]
Message-ID: <m1hbiv6fcb.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4C66FEA9.3040303@kernel.org> (Yinghai Lu's message of "Sat, 14 Aug 2010 13:38:01 -0700")
Yinghai Lu <yinghai@kernel.org> writes:
> For 32bit mptable path, setup_ids_from_mpc() always write io apic id
> register, even there is no change needed.
>
> So try to do that when they are different bewteen reading out and
> mptable
What is the advantage of not writing the value?
Eric
next prev parent reply other threads:[~2010-08-15 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 20:38 [PATCH] x86: Don't write io_apic ID if it is not changed Yinghai Lu
2010-08-15 8:24 ` Cyrill Gorcunov
2010-08-15 8:30 ` Cyrill Gorcunov
2010-08-16 9:06 ` Cyrill Gorcunov
2010-08-15 15:55 ` Eric W. Biederman [this message]
2010-08-16 7:28 ` Ingo Molnar
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=m1hbiv6fcb.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox