From: Balbir Singh <bsingharora@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, Cedric Le Goater <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [TRIVIAL][RFC][PATCH] FU exceptions should carry a cause (IC)
Date: Thu, 10 Nov 2016 14:45:42 +1100 [thread overview]
Message-ID: <f6c127cd-0f77-7177-b98e-fbd912570d58@gmail.com> (raw)
In-Reply-To: <20161110024654.GF18060@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On 10/11/16 13:46, David Gibson wrote:
> On Thu, Nov 10, 2016 at 01:06:17PM +1100, David Gibson wrote:
>> On Thu, Nov 10, 2016 at 12:42:37PM +1100, Balbir Singh wrote:
>>>
>>>
>>> As per the ISA we need a cause for FU exceptions.Executing a tabort r9
>>> for example in libc, causes a EXCP_FU exception. We don't wire up the
>>> IC (cause) when we post the exception. The cause is required
>>> for the kernel to do the right thing. I caught this issue while testing
>>> the latest kernel against Cedrics' latest pnv ipmi branch.
>>>
>>> Signed-off-by: Balbir singh <bsingharora@gmail.com>
>>
>> Applied to ppc-for-2.8
>
> Or not..
>
> This causes compile breakage for the ppc32 targets.
>
Sorry, I'll double check, I did a minimal compile.
I'll redo and repost
Balbir Singh.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-10 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 1:42 [Qemu-devel] [TRIVIAL][RFC][PATCH] FU exceptions should carry a cause (IC) Balbir Singh
2016-11-10 2:06 ` David Gibson
2016-11-10 2:46 ` David Gibson
2016-11-10 3:45 ` Balbir Singh [this message]
2016-11-10 4:37 ` [Qemu-devel] [PATCH v2] " Balbir Singh
2016-11-10 23:50 ` David Gibson
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=f6c127cd-0f77-7177-b98e-fbd912570d58@gmail.com \
--to=bsingharora@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).