Public bug reported:
I'm using Mac OS 10.9.4 with qemu-system-arm installed from brew
(version 1.7.1) and verified with qemu-system-x86_64. I'm trying to pass
a Ralink 5370 WiFi USB dongle to my guest system, it appears in my
system profiler as:
802.11 n WLAN:
Product ID: 0x5370
Vendor ID:
I'll give it a shot, thanks :)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1369347
Title:
Mac OS X cannot passthrough USB device to guest
Status in QEMU:
New
Bug description:
I'm using Mac
For future googlers, I first ran "brew uninstall qemu" then "brew
install libusb".
After that, download the source, "./configure", "make", "sudo make
install" and you're done.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Public bug reported:
using the latest build from git (hash 041ccc922ee474693a2869d4e3b59e920c739bc0
) and all older versions i have tested.
i am using an amd64 host with an arm chroot using "qemu-user arm cortex-a8" cpu
emulation to run it
building coreutils hangs on "checking whether printf su
I am currently experiencing this on Mac OS X 10.8 also, custom built
yesterday evening from the master branch.
I have looked at the diff and it looks like it has been applied in qemu-
thread-posix.c file, but no luck.
Any pointers? Thanks
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 989452 ***
https://bugs.launchpad.net/bugs/989452
He means disabling kerberos authentication in your SSH client config,
whether it be globally in /etc/ssh/ssh_config or ~/.ssh/config, assuming
you're using qemu+ssh:// to migrate your VMs. Either way, this doe
Did this bug come back, or is "error while reading" unrelated but
similar?
Oh look, Debian is using an old version, what are the odds?
Distributor ID: Debian
Description:Debian GNU/Linux 6.0.6 (squeeze)
Release:6.0.6
Codename: squeeze
root@nakvm:~# qemu-img --help
qemu-img versi
Or an old copy because Ubuntu proffers 1.0 which works fine on the same
image.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/826363
Title:
qemu-img convert does not work with vdi files
Status in Q
Has anyone considered a paravirt approach? That is:
Guest kernel: Write a new IOMMU API back end which does KVM hypercalls.
Exposes VFIO to guest user processes (nested VMs) as usual.
Host kernel: KVM does things like collapse {guest_va -> guest_pa ->
host_pa} mappings to {guest_va -> host_pa}
Sorry. Resending in plain text. (Gmail).
-- Forwarded message --
Has anyone considered a paravirt approach? That is:
Guest kernel: Write a new IOMMU API back end which does KVM
hypercalls. Exposes VFIO to guest user processes (nested VMs) as
usual.
Host kernel: KVM does thin
#x27;d agree that incremental approach here is key. VFIO has already seen a
ton of rework to accommodate all architectures. Let's not bite off a bunch
of these other subsystem rewrites in the same chunk as our VFIO effort.
-Aaron
I'm going to send out chunks of comments as I go over this stuff. Below
I've covered the documentation file and vfio_iommu.c. More comments coming
soon...
On 11/3/11 1:12 PM, "Alex Williamson" wrote:
> VFIO provides a secure, IOMMU based interface for user space
> drivers, including device ass
re subsystem by default on certain hardware.
I think the issue is more that the ability to create fake MSI interrupts can
lead to bigger exploits.
Originally we didn't have this parameter. It was added it to reflect the
fact that MSI's triggered by guests are dangerous without the iso
On 8/23/11 10:01 AM, "Alex Williamson" wrote:
> On Tue, 2011-08-23 at 16:54 +1000, Benjamin Herrenschmidt wrote:
>> On Mon, 2011-08-22 at 17:52 -0700, aafabbri wrote:
>>
>>> I'm not following you.
>>>
>>> You have to enforce group/iommu domain assignment whether you have the
>>> existing uio
merge groups
together to conserve IOMMU resources (assuming we're not going to expose
uiommu).
-Aaron
On 8/26/11 12:35 PM, "Chris Wright" wrote:
> * Aaron Fabbri (aafab...@cisco.com) wrote:
>> On 8/26/11 7:07 AM, "Alexander Graf" wrote:
>>> Forget the KVM case for a moment and think of a user space device driver. I
>>> as
>>> a user
get started in understanding
the source code?
What knowledge are required to understand the source code?
BTW, i know this project is not that simple to understand, but I would like to
try, even I need to know a lot
of other knowledge before that, but at least let me get started.
Thanks
-Aaron
Hi Bastian,
Thanks for you suggestion, I decide to do as you said, started by picking some
interesting parts.
-Aaron
On Oct 7, 2015, at 1:04 AM, Bastian Koppelmann
wrote:
Hi Aaron,
On 10/06/2015 04:17 PM, Aaron Elkins wrote:
> Hi all,
>
> I am new to Qemu, and I’m extremely i
Hi peter,
Thanks for suggestion.
Computer hardware architecture, that’s an interesting thing.
-Aaron
On Oct 7, 2015, at 4:08 AM, Peter Crosthwaite
wrote:
On Tue, Oct 6, 2015 at 7:17 AM, Aaron Elkins wrote:
> Hi all,
>
> I am new to Qemu, and I’m extremely interested in understa
Hi all,
I am currently working on Mac OS X 10.11 (El Capitan), and I want to know if I
can build Qemu on it? and how?
Thanks
-Aaron
Alistair,
On Feb 03 16:34, Alistair Francis wrote:
> This patch set is based on the patch sent by Christopher Covington and
> written by Aaron Lindsay which was sent as an RFC (Implement remaining
> PMU functionality).
These patches look like a good start to improving the PMU support,
t
On Feb 04 10:52, Alistair Francis wrote:
> On Thu, Feb 4, 2016 at 5:39 AM, Aaron Lindsay wrote:
> > Please add my
> > Signed-off-by: Aaron Lindsay
> > to all three.
>
> Ok, I wasn't sure what you wanted to do there. I'll add them all and
> they will be th
On Feb 09 15:11, Alistair Francis wrote:
> On Tue, Feb 9, 2016 at 9:19 AM, Peter Maydell
> wrote:
> > On 6 February 2016 at 00:55, Alistair Francis
> > wrote:
> >> Signed-off-by: Aaron Lindsay
> >> Signed-off-by: Alistair Francis
> >> Tested-by:
Public bug reported:
This bug is present as of the latest commit:
714487515dbe0c65d5904251e796cd3a5b3579fb
I also saw it in 2.4.1, but that was a distro package.
You can see the bug simply using the following line: qemu-system-i386
-hda freedos.disk
Simply type vim (or rhide) and start entering
I am still having this error even though I compile from the master
branch and commit a795ef8dcb8cbadffc996c41ff38927a97645234 is definitely
there.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1087114
On line 216 of qemu-thread-posix.c I have commented out the
++sem->count; which seems to be the only change made in that commit.
Unfortunately it still crashes with that error.
I have compiled with --enable-debug but not sure how to get a backtrace
or even a log of what goes wrong.
--
You receiv
then got the following warnings and the guest linux can not response to
keyboard and freezes for a period of time, and this issue repeated forever
while the guest linux was running.
main-loop: WARNING: I/O thread spun for 1000 iterations
Any idea?
Best regards,
-Aaron
> On Oct 19, 2015, at 4:37 AM, Peter Maydell wrote:
>
> On 18 October 2015 at 20:46, Peter Maydell wrote:
>> On 16 October 2015 at 08:32, Aaron Elkins wrote:
>>> I built Qemu on Mac OS X 10.11 El Capitan with:
>>>
>>>./configu
Public bug reported:
When e500 PPC is booted multi-core, the non-boot cores are started via
the spin table. ppce500_spin.c:spin_kick() calls
mmubooke_create_initial_mapping() to allocate a 64MB TLB entry, but
the created TLB entry is only 256KB.
The root cause is that the function computing the
"Daniel P. Berrange" writes:
> On Tue, Jun 14, 2016 at 04:03:43PM +0800, Wei Xu wrote:
>> On 2016年06月09日 05:48, Aaron Conole wrote:
>> > Flavio Leitner writes:
>> >
>> > > Adding Aaron who is fixing exactly that on the OVS side.
>> > &
Wei Xu writes:
> On 2016年06月09日 05:48, Aaron Conole wrote:
>> Flavio Leitner writes:
>>
>>> Adding Aaron who is fixing exactly that on the OVS side.
>>>
>>> Aaron, please see the last question in the bottom of this email.
>>>
>>>
.
Simply changing MAS1_TSIZE_SHIFT from 7 to 8 is not appropriate since
the macro is used elsewhere.
Signed-off-by: Aaron Larson
---
hw/ppc/ppce500_spin.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/ppc/ppce500_spin.c b/hw/ppc/ppce500_spin.c
index 76bd78b..7e38f0c
ppce500_spin.c uses SPR_PIR to initialize the spin table, however on
Book E processors the correct SPR is SPR_BOOKE_PIR.
Signed-off-by: Aaron Larson
---
hw/ppc/ppce500_spin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/ppc/ppce500_spin.c b/hw/ppc/ppce500_spin.c
index
Hi all,
I tried this once before using command-line parameters and it was
knocked back. Someone made the mention of using options so I had a
look and saw that it was really simple to do.
The following is a patch from the latest Git snapshot. I have also
attached it (in case it gets broken by Gm
ect a
patch from me in the coming days.
Cheers
sent from my Telstra NEXTG handset
-Original Message-
From: Kevin Wolf
Sent: Tuesday, 3 August 2010 10:47 PM
To: Alexander Graf
Cc: qemu-devel List ; Aaron Mason
Subject: Re: [PATCH] Block: Support creation of SCSI VMDK images in qem
Hi,
Now that I have half a clue, please find attached a properly formatted
patch for the above with a signed-off line. Hopefully attaching it
won't cause issues as I have winblows on this machine and can't get
git send-email to work at this time.
Regards
0001-Added-an-option-to-set-the-VMDK-ad
there
sent from my Telstra NEXTG™ handset
-Original Message-
From: Kevin Wolf
Sent: Wednesday, 4 August 2010 10:29 PM
To: andrzej zaborowski
Cc: Aaron Mason ; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Added an option to set the VMDK adapter type
Am 04.08.2010 14:27
'll fix them on Monday next
time I'm in the office.
On Thu, Aug 5, 2010 at 7:07 AM, Aaron Mason
wrote:
> there
>
> sent from my Telstra NEXTG™ handset
>
> -Original Message-
> From: Kevin Wolf
> Sent: Wednesday, 4 August 2010 10:29 PM
> To: andrzej zabo
xe -L "path_to_my_mandrake_image"
Nothing happened, I just get the prompt back without any errors. Is
there any way for me to get a more informative error messages when I'm
trying to boot?
Thanx in advance
Aaron Feng
___
Qemu-devel mailing list
Qemu-d
ail down the
failure case and/or help in working towards an appropriate solution.
Thanks!
-Aaron
Sorry, left off the very end of my timeline:
On Nov 18 16:58, Aaron Lindsay wrote:
> I have, so far, discovered the following timeline:
> 1. My plugin receives a instruction execution callback for a load
>instruction. At this time, cpu->plugin_mem_cbs points to the same
>me
Hi,
When bypass iommu is used together with split irqchip, during boot,
kernel would dump 2 callstacks(see attached) and the results are pci
devices attached to root bus will fall back to using IOAPIC instead of
MSIx. This problem was initally noticed by Juro.
This only happens with kernel-irqchi
From: Aaron Dominick
---
hw/display/r300.c | 9 +
hw/display/r300.h | 6 ++
2 files changed, 15 insertions(+)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 653474c3aa..074dbf5b2d 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -878,6 +878,15 @@ static void
From: Aaron Dominick
---
hw/display/r300.c | 9 +
hw/display/r300.h | 6 ++
2 files changed, 15 insertions(+)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 653474c3aa..074dbf5b2d 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -878,6 +878,15 @@ static void
From: Aaron Dominick
---
hw/display/ati.c | 9 +-
hw/display/r300.c | 571 +-
hw/display/r300.h | 77 ++-
3 files changed, 544 insertions(+), 113 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index db3b254316..1d36233163
From: Aaron Dominick
---
hw/display/r300.c | 15 ---
hw/display/r300.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 94e90b7a95..653474c3aa 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -278,6 +278,10
From: Aaron Dominick
Hello,
I thought of working on an emulated R300 GPU for QEMU video acceleration on
vintage operating systems (Windows 9x-XP)
The following patch series contains the initial QEMU device and some register
read/write operations.
Testing it on an OpenSUSE Linux guest and the
From: Aaron Dominick
---
hw/display/r300.c | 15 ---
hw/display/r300.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 94e90b7a95..653474c3aa 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -278,6 +278,10
From: Aaron Dominick
---
hw/display/ati.c | 9 +-
hw/display/r300.c | 571 +-
hw/display/r300.h | 77 ++-
3 files changed, 544 insertions(+), 113 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index db3b254316..1d36233163
Tue, Nov 26, 2019 at 5:33 PM BALATON Zoltan wrote:
> Hello,
>
> On Tue, 26 Nov 2019, aaron.zakh...@gmail.com wrote:
> > From: Aaron Dominick
> >
> > Hello,
> > I thought of working on an emulated R300 GPU for QEMU video acceleration
> on vintage operating syste
From: Aaron Dominick
I have removed the botched patches and have got the code working upto the GART
initialization.
I am not sure how to implement the GART. I am guessing it should be an IOMMU
device but I think that is a bit much for an emulated card.
The earlier problem of display probing
From: Aaron Dominick
---
hw/display/r300.c | 15 ---
hw/display/r300.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 94e90b7a95..653474c3aa 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -278,6 +278,10
From: Aaron Dominick
---
hw/display/ati.c | 9 +-
hw/display/r300.c | 571 +-
hw/display/r300.h | 77 ++-
3 files changed, 544 insertions(+), 113 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index db3b254316..1d36233163
From: Aaron Dominick
---
hw/display/r300.c | 9 +
hw/display/r300.h | 6 ++
2 files changed, 15 insertions(+)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 653474c3aa..074dbf5b2d 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -878,6 +878,15 @@ static void
From: Aaron Dominick
This is the cleaned up patchset to my previous RFC patch set.
I could not reliably clean up my previous commits so I deleted my fork and
started from scratch.
The patch looks like a lot of changes but most of it is just register
definitions copied from the kernel radeon
I tested my code with the vgabios-ati.bin rom file and it seems to get
passed the earlier issue I had.
I have cleaned up my code and have sent a new patch series. The new one is
pretty big but it contains only the necessary header files and it should be
a little easier to review
On Wed, Nov 27, 20
From: Aaron Dominick
---
hw/display/ati.c | 9 +-
hw/display/r300.c | 571 +-
hw/display/r300.h | 77 ++-
3 files changed, 544 insertions(+), 113 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index db3b254316..1d36233163
From: Aaron Dominick
---
hw/display/r300.c | 15 ---
hw/display/r300.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 94e90b7a95..653474c3aa 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -278,6 +278,10
From: Aaron Dominick
---
hw/display/r300.c | 15 ---
hw/display/r300.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 94e90b7a95..653474c3aa 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -278,6 +278,10
From: Aaron Dominick
---
hw/display/r300.c | 9 +
hw/display/r300.h | 6 ++
2 files changed, 15 insertions(+)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 653474c3aa..074dbf5b2d 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -878,6 +878,15 @@ static void
From: Aaron Dominick
---
hw/display/r300.c | 9 +
hw/display/r300.h | 6 ++
2 files changed, 15 insertions(+)
diff --git a/hw/display/r300.c b/hw/display/r300.c
index 653474c3aa..074dbf5b2d 100644
--- a/hw/display/r300.c
+++ b/hw/display/r300.c
@@ -878,6 +878,15 @@ static void
From: Aaron Dominick
---
hw/display/ati.c | 9 +-
hw/display/r300.c | 571 +-
hw/display/r300.h | 77 ++-
3 files changed, 544 insertions(+), 113 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index db3b254316..1d36233163
From: Aaron Hill
This commit properly sets the ENET_BD_BDU flag once the emulated FEC controller
has finished processing the last descriptor. This is done for both transmit
and receive descriptors.
This allows the QNX 7.0.0 BSP for the Sabrelite board (which can be
found at http
Public bug reported:
The imx_eth_update function in hw/net/imx_fec.c has the following
comment
(https://github.com/qemu/qemu/blob/864ab314f1d924129d06ac7b571f105a2b76a4b2/hw/net/imx_fec.c#L421-L445):
/*
* Previous versions of qemu had the ENET_INT_MAC and ENET_INT_MAC
* interrupts s
On Jan 08 11:47, Emilio Cota wrote:
> Related: #1381
>
> Signed-off-by: Emilio Cota
> ---
> accel/tcg/translator.c | 15 ++-
> 1 file changed, 10 insertions(+), 5 deletions(-)
Tested-by: Aaron Lindsay
on.
>
> Related: #1381
>
> Signed-off-by: Emilio Cota
> ---
> accel/tcg/plugin-gen.c | 26 ++
> include/qemu/plugin.h | 7 +++
> 2 files changed, 25 insertions(+), 8 deletions(-)
Tested-by: Aaron Lindsay
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 65 +--
target/arm/tcg/pauth_helper.c | 2 +-
2 files changed, 63 insertions(+), 4 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index f0f27f259d..868d844d5a 100644
--- a/target/arm
feature
for ARMv8.3.
Signed-off-by: Aaron Lindsay
Reviewed-by: Richard Henderson
---
target/arm/helper-a64.h| 4 ++
target/arm/tcg/pauth_helper.c | 71 +++---
target/arm/tcg/translate-a64.c | 20 +-
3 files changed, 72 insertions(+), 23 deletions(-)
dif
code formatting fixes and logic simplifications
[0] - https://lists.nongnu.org/archive/html/qemu-devel/2023-02/msg06494.html
Aaron Lindsay (8):
target/arm: Add ID_AA64ISAR2_EL1
target/arm: v8.3 PAC ID_AA64ISAR[12] feature-detection
target/arm: Implement v8.3 QARMA3 PAC cipher
targe
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
Reviewed-by: Richard Henderson
---
target/arm/tcg/pauth_helper.c | 54 ---
1 file changed, 44 insertions(+), 10 deletions(-)
diff --git a/target/arm/tcg/pauth_helper.c b/target/arm/tcg/pauth_helper.c
index
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
Reviewed-by: Richard Henderson
---
target/arm/tcg/pauth_helper.c | 33 +++--
1 file changed, 23 insertions(+), 10 deletions(-)
diff --git a/target/arm/tcg/pauth_helper.c b/target/arm/tcg/pauth_helper.c
index
Signed-off-by: Aaron Lindsay
---
target/arm/syndrome.h | 7 +++
target/arm/tcg/pauth_helper.c | 16
2 files changed, 23 insertions(+)
diff --git a/target/arm/syndrome.h b/target/arm/syndrome.h
index d27d1bc31f..bf79c539d9 100644
--- a/target/arm/syndrome.h
+++ b
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 1 +
target/arm/cpu64.c | 48 +++---
2 files changed, 34 insertions(+), 15 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 868d844d5a..80683c428f 100644
--- a/target/arm/cpu.h
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
Reviewed-by: Richard Henderson
---
target/arm/tcg/pauth_helper.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/target/arm/tcg/pauth_helper.c b/target/arm/tcg/pauth_helper.c
index 122c208de2
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 1 +
target/arm/helper.c | 4 ++--
target/arm/hvf/hvf.c | 1 +
target/arm/kvm64.c | 2 ++
4 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index c097cae988..f0f27f259d 100644
--- a/target
On Feb 22 11:37, Richard Henderson wrote:
> On 2/22/23 09:35, Aaron Lindsay wrote:
> > @@ -406,6 +421,16 @@ static uint64_t pauth_auth(CPUARMState *env, uint64_t
> > ptr, uint64_t modifier,
> > uint64_t xor_mask = MAKE_64BIT_MASK(bot_bit, top_b
On Feb 22 12:14, Richard Henderson wrote:
> On 2/22/23 09:35, Aaron Lindsay wrote:
> > +static Property arm_cpu_pauth2_property =
> > +DEFINE_PROP_BOOL("pauth2", ARMCPU, prop_pauth2, false);
> > +static Property arm_cpu_pauth_fpac_property =
> > +
ests.
Is there any commonality in the storage format being used? Is it
qcow2? Is it network-backed?
There are reports with local ZFS volumes, local LVM-Thin volumes, RBD
images, qcow2 on NFS. So no pattern to be seen.
Apologies for the "tier 1" questions.
Thank you for your time!
On Feb 13 17:11, Peter Maydell wrote:
> On Thu, 2 Feb 2023 at 21:12, Aaron Lindsay
> wrote:
> >
> > Signed-off-by: Aaron Lindsay
> > ---
> > target/arm/cpu.h | 5 +++
> > target/arm/cpu64.c | 81 ++
> &
On Feb 13 16:01, Peter Maydell wrote:
> On Thu, 2 Feb 2023 at 21:13, Aaron Lindsay
> wrote:
> > +static inline bool isar_feature_aa64_pauth_epac(const ARMISARegisters *id)
> > +{
> > +return isar_feature_pauth_get_features(id) == 0b0010;
>
> This should
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 61 +--
target/arm/helper.c | 4 +--
target/arm/pauth_helper.c | 2 +-
3 files changed, 61 insertions(+), 6 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 8cf70693be
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
---
target/arm/pauth_helper.c | 32 ++--
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index a83956652f..c4ee040da7 100644
--- a/target/arm
feature
for ARMv8.3.
Signed-off-by: Aaron Lindsay
---
target/arm/helper-a64.h| 4 +++
target/arm/pauth_helper.c | 71 +++---
target/arm/translate-a64.c | 20 +--
3 files changed, 72 insertions(+), 23 deletions(-)
diff --git a/target/arm/helper-a64.h b/t
vious patchset - I'm planning to await further discussion about the
appropriate way to organize them before making those changes and
particularly welcome further review there.
-Aaron
[0] https://lists.nongnu.org/archive/html/qemu-devel/2023-02/msg00660.html
Aaron Lindsay (7):
target/arm:
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
---
target/arm/pauth_helper.c | 50 +++
1 file changed, 40 insertions(+), 10 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index e5206453f6..f525ef7fad 100644
--- a
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 5 +++
target/arm/cpu64.c | 81 ++
2 files changed, 72 insertions(+), 14 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 9c3cbc9a29..40b4631f11 100644
--- a/target/arm/cpu.h
Signed-off-by: Aaron Lindsay
Reviewed-by: Peter Maydell
---
target/arm/pauth_helper.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index f525ef7fad..a83956652f 100644
--- a/target/arm/pauth_helper.c
Signed-off-by: Aaron Lindsay
---
target/arm/pauth_helper.c | 35 ++-
target/arm/syndrome.h | 7 +++
2 files changed, 37 insertions(+), 5 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index 96770d7860..db6cf9b5bc 100644
Pavel's "replay: rewrite async event handling" commit [2]. Commits prior to
that one boot successfully (neither assertions nor hangs) with `-icount 0 -smp
2`.
I've looked over these two commits ([1], [2]), but it is not obvious to me
how/why they might be interacting to produce the
On Oct 21 17:00, Peter Maydell wrote:
> On Fri, 21 Oct 2022 at 16:48, Aaron Lindsay
> wrote:
> >
> > Hello,
> >
> > I am encountering one or more bugs when using -icount and -smp >1 that I am
> > attempting to sort out. My current theory is that it is an
Signed-off-by: Aaron Lindsay
---
target/arm/pauth_helper.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index f525ef7fad..a83956652f 100644
--- a/target/arm/pauth_helper.c
+++ b/target/arm/pauth_helper.c
feature
for ARMv8.3.
Signed-off-by: Aaron Lindsay
---
target/arm/helper-a64.h| 4 +++
target/arm/pauth_helper.c | 63 --
target/arm/translate-a64.c | 20 ++--
3 files changed, 68 insertions(+), 19 deletions(-)
diff --git a/target/arm/helper-a64.h b/t
Hello,
I've taken a first pass at implementing many of the ARMv8.3 Pointer
Authentication features and welcome your review.
Thanks!
-Aaron
Aaron Lindsay (7):
target/arm: v8.3 PAC ID_AA64ISAR[12] feature-detection
target/arm: Implement v8.3 QARMA3 PAC cipher
target/arm: Implement
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 5 +++
target/arm/cpu64.c | 81 ++
2 files changed, 72 insertions(+), 14 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 9be59163ff..a9420bae67 100644
--- a/target/arm/cpu.h
Signed-off-by: Aaron Lindsay
---
target/arm/cpu.h | 57 ---
target/arm/helper.c | 4 +--
target/arm/pauth_helper.c | 4 +--
3 files changed, 58 insertions(+), 7 deletions(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 8cf70693be
Signed-off-by: Aaron Lindsay
---
target/arm/pauth_helper.c | 48 +++
1 file changed, 39 insertions(+), 9 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index a0c9bea06b..f525ef7fad 100644
--- a/target/arm/pauth_helper.c
+++ b
Signed-off-by: Aaron Lindsay
---
target/arm/pauth_helper.c | 29 +++--
1 file changed, 19 insertions(+), 10 deletions(-)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index a83956652f..6ebf6df75c 100644
--- a/target/arm/pauth_helper.c
+++ b/target
Signed-off-by: Aaron Lindsay
---
target/arm/pauth_helper.c | 26 ++
target/arm/syndrome.h | 6 ++
2 files changed, 32 insertions(+)
diff --git a/target/arm/pauth_helper.c b/target/arm/pauth_helper.c
index 66dc90a289..3a2772de0e 100644
--- a/target/arm
Emilio,
On Dec 18 00:24, Emilio Cota wrote:
> On Tue, Nov 29, 2022 at 15:37:51 -0500, Aaron Lindsay wrote:
> (snip)
> > > Does this hint that there are cases where reset cpu->plugin_mem_cbs to
> > > NULL is
> > > getting optimized away, but not the code to se
es appear in a DRHD's
device scope.
Enhance the document by mentioning what could happen when bypass_iommu
is used under Linux guest.
For detailed qemu cmdline and guest kernel dmesg, please see:
https://lore.kernel.org/qemu-devel/20240510072519.GA39314@ziqianlu-desk2/
Reported-by: Juro Bystrick
1 - 100 of 498 matches
Mail list logo
