From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: <linuxppc-dev@linux.freescale.net>,
Scott Wood <scottwood@freescale.com>,
Anatolij Gustschin <agust@denx.de>, <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] [for 3.4] drivers/virt: the Freescale hypervisor driver doesn't need to check MSR[GS]
Date: Sun, 25 Nov 2012 07:07:31 -0600 [thread overview]
Message-ID: <AB770BBF-9E2B-461F-B0A9-F141517EBEDD@kernel.crashing.org> (raw)
In-Reply-To: <1337281828-31120-1-git-send-email-timur@freescale.com>
On May 17, 2012, at 2:10 PM, Timur Tabi wrote:
> The MSR[GS] bit indicates whether the kernel is running in processor guest
> state mode, but such a check is unnecessary. The driver already checks
> for the /hypervisor node and the fsl,hv-version property, so it already
> knows that it's running under the Freescale hypervisor.
>
> There is nothing in the driver that inherently requires guest state,
> anyway.
>
> This fixes a break that can occur in some randconfig builds.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> drivers/virt/fsl_hypervisor.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
applied to next
- k
prev parent reply other threads:[~2012-11-25 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 19:10 Timur Tabi
2012-05-17 19:10 ` [PATCH 2/2] [for 3.4] powerpc/512x: don't compile any platform DIU code if the DIU is not enabled Timur Tabi
2012-10-15 15:03 ` [PATCH 1/2] [for 3.4] drivers/virt: the Freescale hypervisor driver doesn't need to check MSR[GS] Tabi Timur-B04825
2012-11-25 13:07 ` Kumar Gala [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=AB770BBF-9E2B-461F-B0A9-F141517EBEDD@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=agust@denx.de \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@linux.freescale.net \
--cc=scottwood@freescale.com \
--cc=timur@freescale.com \
/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®