From: Alexander Graf <agraf@suse.de>
To: qemu-ppc@nongnu.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, blauwirbel@gmail.com,
anthony@codemonkey.ws, aurelien@aurel32.net,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH 1/9] pseries: Factor out check for out-of-bounds LIOBN
Date: Mon, 6 May 2013 17:25:09 +0200 [thread overview]
Message-ID: <1367853917-2015-2-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1367853917-2015-1-git-send-email-agraf@suse.de>
From: David Gibson <david@gibson.dropbear.id.au>
PAPR defines LIOBNs (Logical IO Bus Numbers) to be 32-bit, and we check for
values that aren't in the code for H_PUT_TCE. This patch factors the check
into spapr_tce_find_by_liobn(), which already checks if a 32-bit LIOBN
actually exists. This will become more important as future patches add
other hypercalls which need to look up a LIOBN.
At the same time we fix the typo in the message.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Alexander Graf <agraf@suse.de>
---
hw/ppc/spapr_iommu.c | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/ppc/spapr_iommu.c b/hw/ppc/spapr_iommu.c
index d2782cf..c6aa4fe 100644
--- a/hw/ppc/spapr_iommu.c
+++ b/hw/ppc/spapr_iommu.c
@@ -55,6 +55,12 @@ static sPAPRTCETable *spapr_tce_find_by_liobn(uint32_t liobn)
{
sPAPRTCETable *tcet;
+ if (liobn & 0xFFFFFFFF00000000ULL) {
+ hcall_dprintf("Request for out-of-bounds LIOBN 0x" TARGET_FMT_lx "\n",
+ liobn);
+ return NULL;
+ }
+
QLIST_FOREACH(tcet, &spapr_tce_tables, list) {
if (tcet->liobn == liobn) {
return tcet;
@@ -218,12 +224,6 @@ static target_ulong h_put_tce(PowerPCCPU *cpu, sPAPREnvironment *spapr,
target_ulong tce = args[2];
sPAPRTCETable *tcet = spapr_tce_find_by_liobn(liobn);
- if (liobn & 0xFFFFFFFF00000000ULL) {
- hcall_dprintf("spapr_vio_put_tce on out-of-boundsw LIOBN "
- TARGET_FMT_lx "\n", liobn);
- return H_PARAMETER;
- }
-
ioba &= ~(SPAPR_TCE_PAGE_SIZE - 1);
if (tcet) {
--
1.6.0.2
next prev parent reply other threads:[~2013-05-06 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 15:25 [Qemu-devel] [PULL 1.5 0/9] ppc patch queue 2013-05-06 Alexander Graf
2013-05-06 15:25 ` Alexander Graf [this message]
2013-05-06 15:25 ` [Qemu-devel] [PATCH 2/9] pseries: Fix debug message for out-of-bounds address in H_PUT_TCE Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 3/9] PPC: e500: initialize GPRs as per epapr Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 4/9] pseries: Update SLOF firmware image Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 5/9] PPC: Add MMU type for 2.06 with AMR but no TB pages Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 6/9] target-ppc: Fix invalid SPR read/write warnings Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 7/9] target-ppc: Add read and write of PPR SPR Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 8/9] PPC: e500: correct params->ram_size with ram_size Alexander Graf
2013-05-06 15:25 ` [Qemu-devel] [PATCH 9/9] spapr_llan: fix device reenabling Alexander Graf
2013-05-06 18:21 ` [Qemu-devel] [PULL 1.5 0/9] ppc patch queue 2013-05-06 Aurelien Jarno
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=1367853917-2015-2-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--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).