From: Rick Jones <rick.jones2@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Ensure PSR.ac is cleared for early userspace
Date: Mon, 17 Nov 2008 19:52:22 +0000 [thread overview]
Message-ID: <4921CB76.9060807@hp.com> (raw)
In-Reply-To: <200811120135.mAC1ZoSd017352@agluck-lia64.sc.intel.com>
Luck, Tony wrote:
>>If the hypothesis is that test and development kernels would catch the
>>alignment problems, then there shouldn't be any in the production
>>kernels right? However, if there _are_ any out there in production
>>don't we want them to become visible? Even on processors which can
>>handle them it is still better to not have the unaligned acesses in the
>>first place right?
>
>
> I was thinking of the case where someone loads a module that has
> not had the benefit of being developed in an environment where all
> the unaligned accesses could be easily seen and removed. It seems
> (to me) that the user of that system would be happier to have the
> flow of "unaligned access" messages on the console reduced by letting
> the h/w handle the ones that it could.
Ignorance being bliss?
If this module was developed in an environment where the unaligned
accesses could not be easily seen how does hiding the messages in
production get them addressed? Modules being developed in such
environments would seem to suggest that the messages _should_ be seen in
production?
rick jones
next prev parent reply other threads:[~2008-11-17 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 1:35 [PATCH] Ensure PSR.ac is cleared for early userspace Luck, Tony
2008-11-13 6:22 ` Isaku Yamahata
2008-11-15 1:38 ` Luck, Tony
2008-11-15 3:03 ` David Mosberger-Tang
2008-11-15 19:57 ` Tony Luck
2008-11-17 18:59 ` Rick Jones
2008-11-17 19:45 ` Luck, Tony
2008-11-17 19:52 ` Rick Jones [this message]
2008-11-17 20:58 ` Luck, Tony
2008-11-18 7:06 ` Petr Tesarik
2008-11-18 7:12 ` Matthew Wilcox
2008-11-18 11:58 ` Robin Holt
2008-11-20 22:45 ` Luck, Tony
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=4921CB76.9060807@hp.com \
--to=rick.jones2@hp.com \
--cc=linux-ia64@vger.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