On 6/4/2025 7:34 PM, Donald Dutile wrote:
On 6/4/25 10:02 PM, Nathan Chen wrote:
On 6/2/2025 8:41 AM, Shameer Kolothum wrote:
This patch series introduces support for a user-creatable SMMUv3 device
(-device arm-smmuv3) in QEMU.
Tested-by: Nathan Chen
I am able to create 16 SMMUv3
On 6/2/2025 8:41 AM, Shameer Kolothum wrote:
This patch series introduces support for a user-creatable SMMUv3 device
(-device arm-smmuv3) in QEMU.
Tested-by: Nathan Chen
I am able to create 16 SMMUv3 devices in a qemu VM with emulated devices
properly associated with the guest SMMUs in
741r...@redhat.com/
[1]
https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/7GDT6RX5LPAJMPP4ZSC4ACME6GVMG236/#X6R52JRBYDFZ5PSJFR534A655UZ3RHKN
Thanks,
Nathan
E_MMIO is worth adding?
Yes, and actually we have a patch ready for the configurable highmem
region size. Matt Ochs will send it out in the next day or so and CC you
on the submission.
adding ""mem-reserve=X" and "io-reserve=X" to pcie-root-port helps
Ok, good to know - I'll keep that in mind for future testing.
Thanks,
Nathan
letting you know I resolved this by increasing the MMIO region size
in hw/arm/virt.c to support passing through GPUs with large BAR regions
(VIRT_HIGH_PCIE_MMIO). Thanks for taking a look.
Thanks,
Nathan
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
with the
boot firmware provided by qemu-efi-aarch64 version 2024.02-2. This
prevents the VM from booting, eventually dropping into the UEFI shell
with an error message indicating DMA mapping failed for the passthrough
devices.
Thanks,
Nathan
l able to attach a
passthrough device behind a PCIe switch and see it attached to a vSMMU
in the VM, so I'm not sure if you need to make additional changes to
your solution to support this. But I think we should still support/test
the case where VFIO devices are behind a switch, otherwise we're placing
a limitation on end users who have a use case for it.
-Nathan
e vfio-pci,host=0009:01:00.0,id=hostdev0,bus=pci.4,addr=0x0 \
-device arm-smmuv3-nested,pci-bus=pci.1
-Nathan
ot-port that is plugged into the
pcie-expander-bus, and multiple pcie-switch-downstream-ports to the
pcie-switch-upstream-port". Future unit-tests should follow this
topology configuration.
Thanks,
Nathan
linux specific boot sequence is skipped
because earlier it is asserted that the linux protocol magic field could not be
found.
Signed-off-by: Nathan Kolpa
---
hw/i386/x86.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/i386/x86.c b/hw/i386/x86.c
index 2b6291ad8d..b59f11
From: "Nathan Egge"
Signed-off-by: Nathan Egge
---
linux-user/syscall.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 95727a816a..38ab2201e2 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
uired
around that '|' (ctx:VxV)
total: 2 errors, 0 warnings, 12 lines checked
❌ FAIL one or more commits failed scripts/checkpatch.pl
The linux-user/syscall.c has many such places where this style check is
failing. Should these be fixed in a separate patch?
Sincerely,
Nathan
From: "Nathan Egge"
Set V bit for hwcap if misa is set.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1793
Signed-off-by: Nathan Egge
---
linux-user/elfload.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linux-user/elfload.c b/linux-user/elflo
One line patch that fixes the issue reported in:
https://gitlab.com/qemu-project/qemu/-/issues/1793
>From 7122a450d745325ce250785e58c543481054bec6 Mon Sep 17 00:00:00 2001
From: "Nathan E. Egge"
Date: Mon, 31 Jul 2023 03:45:13 -0400
Subject: [PATCH] linux-user/elfload: Set V in
error_setg(errp, "dynamic capacity must have backing device");
> +return false;
> +}
> +/* FIXME: set dc as nonvolatile for now */
> +memory_region_set_nonvolatile(dc_mr, true);
> +memory_region_set_enabled(dc_mr, tr
ent->start_dpa <= dpa
> +&& dpa + len <= ent->start_dpa + ent->len) {
> +ret = CXL_MBOX_INVALID_PA;
> +goto out;
> + } else if ((dpa < ent->start_dpa + ent->len
> +&&
r) {
> +error_setg(errp, "dynamic capacity must have backing device");
> +return false;
> +}
> +/* FIXME: set dc as nonvolatile for now */
> +memory_region_set_nonvolatile(dc_mr, true);
> +memory
t;dc.total_extent_count - in->start_extent_id < in->extent_cnt)
> + record_count = ct3d->dc.total_extent_count -
> in->start_extent_id;
> + else
> + record_count = in->extent_cnt;
> +
> + out_pl_len = sizeof(*out) + record_c
;
> + stl_le_p(&out->records[i].dsmadhandle,
> + ct3d->dc.regions[in->start_region_id+i].dsmadhandle);
> + out->records[i].flags
> + = ct3d->dc.regions[in->start_region_id+i].flags;
In this loop your
ze:4 value:0x
> ...
>
Is there going to be a new version of this patch or a different solution
to the poweroff hang then? I am still seeing that with tip of tree QEMU
and I see 8.0.0-rc0 has been tagged; I would hate for this to end up in
a release version.
Cheers,
Nathan
an-swapping.
>
> This should fix some recent reports about poweroff hang.
>
> Fixes: 145e2198d749 ("hw/mips/gt64xxx_pci: Endian-swap using PCI_HOST_BRIDGE
> MemoryRegionOps")
> Signed-off-by: Jiaxun Yang
Thanks for the fix!
Tested-by: Nathan Chancellor
> ---
>
m/fw_cfg.c | 21 ++-
> 10 files changed, 49 insertions(+), 161 deletions(-)
>
> --
> MST
>
For the record, all three of the cases that I tested (i386 no EFI,
x86_64 with and without EFI) worked fine with this series. In case it is
useful:
Tested-by: Nathan Chancellor
Cheers,
Nathan
On Wed, Feb 08, 2023 at 11:14:23AM -0700, Nathan Chancellor wrote:
> On Wed, Feb 08, 2023 at 03:08:35PM -0300, Jason A. Donenfeld wrote:
> > All attempts at providing setup_data have been made as an iteration on
> > whatever was there before, stretching back to the original
> >
setting from x86_load_linux(),
> while leaving intact the infrastructure we'll need in the future to try
> again.
>
> Cc: Michael S. Tsirkin
> Cc: Dov Murik
> Cc: Tom Lendacky
> Cc: Gerd Hoffmann
> Cc: Daniel P. Berrangé
> Cc: Paolo Bonzini
> Cc: Richard
dk2-ovmf 202211-3
I did see a few fixes on qemu-devel for this patch such as [2] but none
I found fixed the issue for me.
If there is any additional information I can provide or patches I can
test, please let me know.
[1]:
https://github.com/ClangBuiltLinux/boot-utils/blob/fec03ef13519e26ac1f
w.
[1]: https://mirrors.edge.kernel.org/pub/tools/crosstool/
[2]:
https://github.com/ClangBuiltLinux/boot-utils/tree/1b837f3b0fca441e0cc694c9b587120e81299554/images/mips
Cheers,
Nathan
# bad: [00b1faea41d283e931256aa78aa975a369ec3ae6] Merge tag
'pull-target-arm-20230123' of https://git.lin
-files/tree/15c1fd6e44622a3c27823d2c5c3083dfc7246146/qemu-2e1f39e29bf9a6b28eaee9fc0949aab50dbad94a
Cheers,
Nathan
I'm mostly looking at AArch64, so they're the same there :) I'm using
this to collect code coverage information, so I have the disassembly,
and it's slightly easier to report it that way; if you think it'd be
more useful on other architectures to report the byte range instead,
it'd be an easy chang
Signed-off-by: Nathan Ringo
---
accel/tcg/trace-events| 2 +-
accel/tcg/translate-all.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/accel/tcg/trace-events b/accel/tcg/trace-events
index 6eefb37f5d..c227e56248 100644
--- a/accel/tcg/trace-events
+++ b/accel/tcg
Updates for QEMU 6.0.0.
This makes it easier to figure out whether a particular instruction was
actually translated.
Signed-off-by: Nathan Ringo
---
accel/tcg/trace-events| 2 +-
accel/tcg/translate-all.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/accel/tcg/trace-events b/accel/tcg
Fixes: 26bab757d41b ("linux-user: Introduce PAGE_ANON")
> Buglink: https://bugs.launchpad.net/bugs/1922617
> Signed-off-by: Richard Henderson
Tested-by: Nathan Chancellor
> ---
> include/exec/cpu-all.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Public bug reported:
This is reproducible against QEMU master. I apologize for the long
reproduction steps, I tried to distill it down as much as possible.
System info:
# qemu-aarch64-static --version
qemu-aarch64 version 5.2.91 (v6.0.0-rc1-68-gee82c086ba)
Copyright (c) 2003-2021 Fabrice Bellard
On Fri, Apr 02, 2021 at 11:25:42AM -0700, Kees Cook wrote:
> On Fri, Apr 02, 2021 at 08:42:07AM +0200, Sedat Dilek wrote:
> > On Thu, Feb 25, 2021 at 10:25 PM Kees Cook wrote:
> > >
> > > On Thu, 11 Feb 2021 12:42:58 -0700, Nathan Chancellor wrote:
> > >
On Mon, Feb 22, 2021 at 11:02:34AM -0800, Nick Desaulniers wrote:
> Did this happen to get picked up already? EOM
I have not gotten an email saying it has been picked up nor does it
appear to be in -next.
Cheers,
Nathan
> On Thu, Feb 11, 2021 at 11:43 AM Nathan Chancellor
ally by the incompatible pointer
types compiler warning. Update fw_cfg_showrev() accordingly.
Fixes: 75f3e8e47f38 ("firmware: introduce sysfs driver for QEMU's fw_cfg
device")
Link: https://github.com/ClangBuiltLinux/linux/issues/1299
Signed-off-by: Nathan Chancellor
---
d
On Mon, Jan 25, 2021 at 11:42:43AM +0100, Paolo Bonzini wrote:
> On 25/01/21 08:10, Nathan Chancellor wrote:
> > > > This patch as commit 5a140b255d ("x86/cpu: Use max host physical address
> > > > if -cpu max option is applied") prevents me from using
On Mon, Jan 25, 2021 at 01:41:50PM +0800, Yang Weijiang wrote:
> On Sun, Jan 24, 2021 at 02:08:29PM -0700, Nathan Chancellor wrote:
> > On Wed, Jan 13, 2021 at 05:04:30PM +0800, Yang Weijiang wrote:
> > > QEMU option -cpu max(max_features) means "Enables all features suppor
hys-bits should be between 32 and 36 (but is 48)
Am I expected to pass "-cpu host,host-phys-bits=false" now or did this
do something unexpected?
Cheers,
Nathan
On Mon, Jan 11, 2021 at 11:04:25AM +0100, Philippe Mathieu-Daudé wrote:
> +Peter
>
> On 1/11/21 2:11 AM, Nathan Chancellor wrote:
> > On Tue, Sep 01, 2020 at 12:40:42PM +0200, Philippe Mathieu-Daudé wrote:
> >> We call pci_register_root_bus() to register 4 IRQs with the
sertion added by this patch triggers while trying to boot a
ppc44x_defconfig Linux kernel:
$ qemu-system-ppc \
-machine bamboo \
-no-reboot \
-append console=ttyS0 \
-display none \
-kernel uImage \
-m 128m \
-nodefaults \
-serial mon:stdio
Linux version 5.11.0-rc3 (nathan@
PPC_SERIAL_MM_BAUDBASE, serial_hd(1),
> DEVICE_BIG_ENDIAN);
> }
> --
> 2.20.1
>
>
Hopefully reporting this here is okay, I find Launchpad hard to use but
I can file it there if need be.
This patch causes a panic while trying to
in_access_size
match reality so that the machine can shut down properly now.
Cc: qemu-sta...@nongnu.org
Fixes: 88a07990fa ("SiFive RISC-V Test Finisher")
Fixes: 5d971f9e67 ("memory: Revert "memory: accept mismatching sizes in
memory_region_access_valid"")
Signed-off-by:
On Sun, Aug 30, 2020 at 08:24:15AM +0100, Mark Cave-Ayland wrote:
> On 30/08/2020 07:49, Nathan Chancellor wrote:
>
> > Unfortunately, it does not. I applied it on top of latest
> > git (ac8b279f13865d1a4f1958d3bf34240c1c3af90d) and I can still
> > reproduce my failure.
On Sun, Aug 30, 2020 at 02:20:38AM -0400, Michael S. Tsirkin wrote:
> On Wed, Aug 26, 2020 at 10:32:16PM -0700, Nathan Chancellor wrote:
> > Hi all,
> >
> > Sorry for the duplicate reply, my first one was rejected by a mailing
> > list administrator for being too l
On Thu, Aug 27, 2020 at 08:53:30AM -0700, Alistair Francis wrote:
> On Wed, Aug 26, 2020 at 11:26 PM Nathan Chancellor
> wrote:
> >
> > Hi all,
> >
> > Sorry for the duplicate reply, my first one was rejected by a mailing
> > list administrator for being to
commit e9f186e514a70557d695cadd2c2287ef97737023
> Author: Peter A. G. Crosthwaite
> Date: Mon Mar 5 14:39:12 2012 +1000
>
> cadence_gem: initial version of device model
>
> Device model for cadence gem ethernet controller.
>
> Signed-off-by: Peter A. G. Crosth
elaxation of the requirement that these exceptions cause
> interrupts when MSR[EE]=1 (e.g., when mtmsr executes to completion as
> TCG is doing here), rather it specifies how a pipelined processor can
> have multiple instructions in flight where one may influence how another
>
On Tue, Apr 14, 2020 at 12:05:53PM +1000, David Gibson wrote:
> On Sat, Apr 11, 2020 at 11:57:23PM +1000, Nicholas Piggin wrote:
> > Nicholas Piggin's on April 11, 2020 7:32 pm:
> > > Nathan Chancellor's on April 11, 2020 10:53 am:
> > >> The tt.config valu
On Sat, Apr 11, 2020 at 11:57:23PM +1000, Nicholas Piggin wrote:
> Nicholas Piggin's on April 11, 2020 7:32 pm:
> > Nathan Chancellor's on April 11, 2020 10:53 am:
> >> The tt.config values are needed to reproduce but I did not verify that
> >> ONLY tt.confi
es using '-nodefaults'. If no BMC
> device are provided, output a warning but let QEMU run as this is a
> supported configuration. However, when multiple BMC devices are
> defined, stop QEMU with a clear error as the results are unexpected.
>
> Fixes: e2392d4395dd ("pp
I assume I will just need to hack up a
check for QEMU 5.0.0+ and just not add those devices? We use that script
with QEMU 3.1.0 in our CI and I use it locally with QEMU 4.2.0 so
universally getting rid of them doesn't seem logical.
Curious for your thoughts on what to do and cheers,
Nathan
I pulled down the fix, built locally, and can confirm that this resolves
the issue. Thank you for the quick patch!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1844597
Title:
fc1120a7f5f2d4b601003
** Attachment added: "aspeed-bmc-opp-romulus.dtb"
https://bugs.launchpad.net/qemu/+bug/1844597/+attachment/5290033/+files/aspeed-bmc-opp-romulus.dtb
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1
Ugh, sorry, I forget that I can actually upload files to these platforms
:(
Done, let me know if you need anything else!
** Attachment added: "zImage"
https://bugs.launchpad.net/qemu/+bug/1844597/+attachment/5290032/+files/zImage
--
You received this bug notification because you are a membe
Public bug reported:
Commit 4cdabee7d6d2 ("ARM: configs: aspeed_g5: Enable AST2600") [1] in
the Linux kernel enabled CONFIG_VFP. When building this config with
Clang, the resulting kernel does not boot after commit fc1120a7f5
("target/arm: Implement NSACR gating of floating point") [2] (present
si
Public bug reported:
Host OS: macOS High Sierra (10.13.6)
MacBook Pro (Retina, Mid 2015)
Processor: 2.8GHz Intel Core i7
Guest OS: OpenBSD 6.4 install media (install64.iso)
Qemu 3.1.0 release, built with:
./configure --prefix=/usr/local/Cellar/qemu/3.1.0_1 --cc=clang
--host-cc=clang
--
I am also able to reproduce this bug. The problem is that when hvf is
enabled, qemu will attempt to execute the xgetbv instruction, which
isn't supported on my processor (Intel Xeon X5670).
Here is a stack trace from lldb; the behavior is 100% reproducible for
me.
nathan@Nathans-Mac-Pro:
Hi,
I'm Nathan Gauër, a french student in computer science.
For this year's Google Summer of Code, I've been selected to work on
the Vulkan support for Virgl3D. The nature of this project makes the
roadmap a bit blurry, but hopefully, we will get somewhere soon.
My mentor wil
Fixed in qemu, yes. But not Ubuntu. Ubuntu strips prebuilt files from
qemu and builds them from source. For sgabios, using the abandoned
source from Google code.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
Any chance of getting this patch included?
I've deleted the incorrect patch and attached the correct one (taken from
QEMU's sgabios repo).
** Patch removed: "0001-SGABIOS-fix-wrong-video-attrs-for-int-10h-ah-13h.patch"
https://bugs.launchpad.net/ubuntu/+source/sgabios/+bug/1670509/+attachment
Hi all,
I'm Nathan Gauër, a GSoC 17 student.
My goal was to provide a PoC OpenGL driver for Windows.
Status:
This project contains two main parts: the OpenGL driver (ICD) and the
kernel driver (DOD).
An Escape handler had to be created on the current DOD driver, and is
now merged on the
Public bug reported:
I've got a guest only network and I'm wanting to access SSH on one of the
guests externally.
I'm using -netdev user,id=usernet0,hostfwd=tcp::-:22,restrict=yes -device
virtio-net-pci,netdev=usernet0
to forward to 22 in the guest.
The docs state:
restrict=on|off
On 5 January 2017 at 01:27, Daniel P. Berrange wrote:
> On Thu, Jan 05, 2017 at 12:56:52AM +1000, Nathan Rossi wrote:
>> If libgcrypt info is available with pkg-config use it over using the
>> libgcrypt-config. pkg-config is preferred due to is compatibility with
>> cross-c
,
then falling back to use libgcrypt-config if available. This follows a
similar process to how libsdl is handled.
Signed-off-by: Nathan Rossi
---
configure | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index 218df87d21..6558121de8 100755
Public bug reported:
We should be able to specify the umask for 9pfs so that files created by
the guest can be accessed by other users on the host. Currently they're
only accessible by the user running qemu (and of course, root).
** Affects: qemu
Importance: Undecided
Status: New
-
Running SkiFree (1.04 x32) on wine (1.8.3 x32) installed in a gentoo
i686 chroot, all running via qemu-user-i386-static 1.7.0 on a raspberry
pi 2 armv7 host works. It was almost playable at 1920x1080 too!
winecfg worked, notepad.exe worked, and SkiFree worked too.
--
You received this bug notifi
Public bug reported:
Using QEMU 2.7.0 with KVM enabled, when I launch the guest without
options (using the default of gtk), the mouse wheel events are not
propagated to the guest.
When I start qemu using -display sdk, mouse wheel events are properly
forwarded.
I can determine that the guest is n
On 09/21/16 03:00, David Gibson wrote:
On Wed, Sep 21, 2016 at 01:20:57PM +1000, David Gibson wrote:
On Tue, Aug 30, 2016 at 01:02:47AM +, Nathan Whitehorn wrote:
These are mandatory per PAPR and available on Linux 4.3 and newer kernels. The
calls in question are required to run FreeBSD
On Thu, Sep 22, 2016 at 6:40 AM, Alistair Francis
wrote:
> On Wed, Sep 21, 2016 at 11:09 AM, Nathan Rossi wrote:
>> Whilst according to the Zynq TRM this device covers a register region of
>> 0x000 - 0x120. The register region is also shared with XADCIF prefix
>> registe
xadc, id ""
mmio f8007100/0020
Mapping with XLNX_ZYNQ_DEVCFG_R_MAX = 0x100 / 4:
dev: xlnx.ps7-dev-cfg, id ""
mmio f8007000/0100
dev: xlnx,zynq-xadc, id ""
mmio 0000f8007100/0020
Signed-off-by: Nathan Rossi
---
These are mandatory per PAPR and available on Linux 4.3 and newer kernels. The
calls in question are required to run FreeBSD guests with reasonable
performance, so enable them if possible.
Signed-off-by: Nathan Whitehorn
---
hw/ppc/spapr.c | 3 +++
target-ppc/kvm.c | 6
these LMBs are not considered
> by the guest.
>
> Signed-off-by: Bharata B Rao
Reviewed-by: Nathan Fontenot
> ---
> Changes in v4:
>
> - Included address information for all LMBs in ibm,dynamic-memory.
> - Use both RESERVED and DRC_INVALID flag bits for non-hotpluggab
On 06/06/2016 09:47 AM, Bharata B Rao wrote:
> On Mon, Jun 06, 2016 at 09:14:48AM -0500, Nathan Fontenot wrote:
>> On 06/06/2016 06:37 AM, Bharata B Rao wrote:
>>> Memory hotplug can fail for some combinations of RAM and maxmem when
>>> DDW is enabled in the presence o
ed by guest.
What does qemu do if a guest tries to add or remove a reserved LMB?
Asking because the current guest code (drmgr and kernel) does not
take the reserved flag into consideration when searching for lmbs to
add/remove. This seems like something I should be fixed on the guest
side.
-Nath
onse to those
>> calls. IIUC, you are suggesting that lets remove one LMB by index in
>> response to 1st message and remove (count -1) LMBs from where the last
>> removal was done in the previous message.
>
> Yes, that's the idea.
>
>> Since the same code base
On Thu, Feb 4, 2016 at 10:34 AM, Alistair Francis
wrote:
> Signed-off-by: Alistair Francis
Tested-by: Nathan Rossi
> ---
>
> target-arm/helper.c | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/target-arm/helper.c b/target-arm/helper.c
> index
On Thu, Feb 4, 2016 at 10:34 AM, Alistair Francis
wrote:
> This patch adds the following registers including read and write functions:
> PMSELR, PMSELR_EL0, PMXEVCNTR, PMXEVCNTR_EL0, PMXEVTYPER and PMXEVTYPER_EL0.
>
> Signed-off-by: Alistair Francis
Tested-by: Nathan Rossi
>
On Thu, Feb 4, 2016 at 10:34 AM, Alistair Francis
wrote:
> Signed-off-by: Alistair Francis
Tested-by: Nathan Rossi
> ---
>
> target-arm/cpu-qom.h | 2 ++
> target-arm/cpu.c | 2 ++
> target-arm/cpu64.c | 2 ++
> target-arm/helper.c | 8
> 4 file
ons where some LMB's are not
removed and some are.
-Nathan
> Signed-off-by: Bharata B Rao
> ---
> Changes in v1:
> - Got rid of the patch that introduced a field in PCDIMMDevice to track
> DIMM marked for removal since we can track that using within DRC
> object.
&
I just tried running x86 windows program, on x86 wine, on qemu-i386, all
on an arm host. I am also experiencing a hung wine and wineserver. Was
this bug ever fixed?
** Also affects: wine (Gentoo Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you
t;> There may be more changes worth making on is_linux. I don't have the
>>>> patch with the full list of FSBL-related SLCR changes handy and can't
>>>> seem to find it in any modern Yocto trees. Wondering if Yocto still
>>>> supports booting Zynq without F
The GIC in ZynqMP cover a 64K address space, however the actual
registers are decoded within a 4K address space and mirrored at the 4K
boundaries. This change fixes the defined size for these regions as it
was set to 0x4000/16K incorrectly.
Signed-off-by: Nathan Rossi
---
include/hw/arm/xlnx
On 09/04/2015 10:33 AM, Michael Roth wrote:
> Quoting Nathan Fontenot (2015-09-03 13:50:59)
>> On 09/01/2015 10:28 PM, Bharata B Rao wrote:
>>> On Mon, Aug 24, 2015 at 09:01:51AM +0530, Bharata B Rao wrote:
>>>> The hash table size allocated to guest depends on the
memory hotplug
> request can't be fulfilled due to insufficient HTAB size. (Anshuman can
> elaborate on this with the exact description on why it is so hard to
> recover).
>
> Do you think disabling memory hotplug upfront is a reasonable workaround
> for this problem ?
>
&
mbs in the dynamic-reconfiguration property.
Just wanting to make sure I'm understanding how this is working.
Also, since the memory specified in the memory@XXX nodes is not removable this
should not break any of the userspace tools.
-Nathan
> Signed-off-by: B
t;> Quoting David Gibson (2015-01-16 00:21:55)
>>>>>> On Tue, Dec 23, 2014 at 06:30:17AM -0600, Michael Roth wrote:
>>>>>>> From: Nathan Fontenot
>>>>>>>
>>>>>>> Signed-off-by: Nathan Fontenot
>>>>>&
I wasn't sure whether to do this for all the modifiers - my use case
doesn't call for it - so I didn't.
Signed-off-by: Nathan Baum
---
ui/vnc.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/ui/vnc.c b/ui/vnc.c
index a742c90..acfb24e 10064
oesn't call for it - so I didn't.
Signed-off-by: Nathan Baum
---
ui/vnc.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/ui/vnc.c b/ui/vnc.c
index a742c90..200cdd7 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -1893,7 +1893,22 @@ static void do_key_eve
cpu and memory).
This happens after the check exception interrupt. In the guest we determine the
drc index for the pci device being added, then makes this rtas call to get the
device tree updates.
-Nathan
>
>
>> ---
>> hw/ppc/spapr_pci.c | 111
>> ++
> + uint32_t token, uint32_t nargs,
>> + target_ulong args, uint32_t nret,
>> + target_ulong rets)
>> +{
>> +uint32_t indicator = rtas_ld(args, 0);
>> +uint32_t dr
at I was getting at: at least just to get things working
>> for testing, just avoid the PRESENT bits in your hot_add_cpu hook rather
>> than patching the guest. Unfortunately the documentation isn't particularly
>> clear about which of these approaches is more correct as far
On 01/03/14 08:27, Paolo Bonzini wrote:
> Il 02/01/2014 19:23, Nathan Whitehorn ha scritto:
>>>> Let me try to grasp what you're doing here. You're trying to
>>>> figure out how many devices there are attached to the bus. For
>>>> every device y
commands addressed to any other LUN is not specified
by the standard and so is left unchanged. This preserves behavior under Linux
and SLOF, which enumerate possible LUNs by hand and so address no commands
either to LUN 0 or the well-known REPORT_LUNS LUN.
Signed-off-by: Nathan Whitehorn
--
hw/scsi
On 01/02/14 10:31, Alexander Graf wrote:
> On 18.10.2013, at 14:33, Nathan Whitehorn wrote:
>
>> Intercept REPORT_LUNS commands addressed either to SRP LUN 0 or the
>> well-known
>> LUN for REPORT_LUNS commands. This is required to implement the SAM and SPC
>> s
On 01/02/14 10:41, Alexander Graf wrote:
> On 02.01.2014, at 16:31, Alexander Graf wrote:
>
>> On 18.10.2013, at 14:33, Nathan Whitehorn wrote:
>>
>>> Intercept REPORT_LUNS commands addressed either to SRP LUN 0 or the
>>> well-known
>>> LUN
On 01/02/14 10:56, ronnie sahlberg wrote:
> On Thu, Jan 2, 2014 at 7:41 AM, Alexander Graf wrote:
>> On 02.01.2014, at 16:31, Alexander Graf wrote:
>>
>>> On 18.10.2013, at 14:33, Nathan Whitehorn wrote:
>>>
>>>> Intercept REPORT_LUNS commands ad
On 12/02/13 12:58, Paolo Bonzini wrote:
> Il 02/12/2013 18:51, Nathan Whitehorn ha scritto:
>> Any news on this? FreeBSD is unbootable from CDROM devices in
>> QEMU/pseries without this patch.
>> -Nathan
> Acked-by: Paolo Bonzini
>
> Alex, can you pick it up?
Any updates?
-Nathan
; Developers; Andreas Färber; Nathan Rossi
> Subject: Re: [Qemu-devel] [PATCH qom v1 1/1] qom/object.c: Split out
> object and class caches.
>
> Hi
>
> On Wed, Dec 4, 2013 at 1:40 AM, Paolo Bonzini wrote:
> > Il 28/11/2013 05:27, Peter Crosthwaite ha scritto:
> >>
1 - 100 of 319 matches
Mail list logo
