All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1824778@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1824778] Re: PowerPC64: tlbivax does not work for addresses above 4G
Date: Thu, 29 Apr 2021 11:20:39 -0000	[thread overview]
Message-ID: <161969523936.11353.11234357281383676635.malone@soybean.canonical.com> (raw)
In-Reply-To: 155531895115.20861.16647644389038821246.malonedeb@chaenomeles.canonical.com

This is an automated cleanup. This bug report has been moved
to QEMU's new bug tracker on gitlab.com and thus gets marked
as 'expired' now. Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/52


** Changed in: qemu
       Status: New => Expired

** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #52
   https://gitlab.com/qemu-project/qemu/-/issues/52

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824778

Title:
  PowerPC64: tlbivax does not work for addresses above 4G

Status in QEMU:
  Expired

Bug description:
  The tlbivax instruction in QEMU does not work for address above 4G. The reason behind this is a simple 32bit trunction of an address.
  Changing the argument ea from uint32_t to target_ulong for the function booke206_invalidate_ea_tlb() in target/ppc/mmu_helper.c solves the issue.

  I did not reproduce this using Linux so I have no public example for
  reproducing it. However it's a pretty straight forward change.

  Issue can be seen in all version of QEMU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824778/+subscriptions


      reply	other threads:[~2021-04-29 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15  9:02 [Qemu-devel] [Bug 1824778] [NEW] PowerPC64: tlbivax does not work for addresses above 4G Johan Carlsson
2021-04-29 11:20 ` Thomas Huth [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=161969523936.11353.11234357281383676635.malone@soybean.canonical.com \
    --to=1824778@bugs.launchpad.net \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.