Ping^3
This has been on list for a very long time without 3rd party review.
Can I send a PULL?
Regards,
Peter
On Wed, Oct 14, 2015 at 11:42 AM, Alistair Francis
wrote:
> Ping^2
>
> On Thu, Aug 27, 2015 at 2:47 PM, Alistair Francis
> wrote:
>> Ping!
>>
>> On Wed, Jul 29, 2015 at 1:24 PM, Alista
Ping...
On 10/16/2015 04:57 PM, Wen Congyang wrote:
> If quorum's child is broken, we can use mirror job to replace it.
> But sometimes, the user only need to remove the broken child, and
> add it later when the problem is fixed.
>
> It is based on the Kevin's bdrv_swap() related patch:
> http://
Add NVDIMM maintainer
Signed-off-by: Xiao Guangrong
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3144113..865c0cf 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -907,6 +907,13 @@ M: Jiri Pirko
S: Maintained
F: hw/net/rocker/
+NVDI
Function 6 is used to set Namespace Label Data
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
index 8c27b25..5c8be41 100644
--- a/hw/acpi/nvdimm.c
+++ b/hw/acpi/nvdimm.c
@
Function 5 is used to get Namespace Label Data
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 63
1 file changed, 63 insertions(+)
diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
index 67c4699..8c27b25 100644
--- a/hw/acpi/nvdimm.c
Function 4 is used to get Namespace label size
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 87 +++-
1 file changed, 86 insertions(+), 1 deletion(-)
diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
index 300a3aa..67c4699 100644
--- a/h
__DSM is defined in ACPI 6.0: 9.14.1 _DSM (Device Specific Method)
Function 0 is a query function. We do not support any function on root
device and only 3 functions are support for NVDIMM device, Get Namespace
Label Size, Get Namespace Label Data and Set Namespace Label Data, that
means we curren
FIT buffer is not completely mapped into guest address space, so a new
function, Read FIT, function index 0x, is reserved by QEMU to
read the piece of FIT buffer. The buffer is concatenated before _FIT
return
Refer to docs/specs/acpi-nvdimm.txt for detailed design
Signed-off-by: Xiao Guan
NVDIMM devices is defined in ACPI 6.0 9.20 NVDIMM Devices
There is a root device under \_SB and specified NVDIMM devices are under the
root device. Each NVDIMM device has _ADR which returns its handle used to
associate MEMDEV structure in NFIT
We reserve handle 0 for root device. In this patch, w
NFIT is defined in ACPI 6.0: 5.2.25 NVDIMM Firmware Interface Table (NFIT)
Currently, we only support PMEM mode. Each device has 3 structures:
- SPA structure, defines the PMEM region info
- MEM DEV structure, it has the @handle which is used to associate specified
ACPI NVDIMM device we will i
A page staring from 0xFF0 and IO port 0x0a18 - 0xa1b in guest are
reserved for NVDIMM ACPI emulation, refer to docs/specs/acpi_nvdimm.txt
for detailed design
A parameter, 'nvdimm-support', is introduced for PIIX4_PM and ICH9-LPC
that controls if nvdimm support is enabled, it is true on default
Check if the input Arg3 is valid then store it into dsm_in if needed
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
index 53ed675..e179a72 100644
--- a/hw/acpi/
Introduce a parameter, named "reserve-label-data", if it is
false which indicates that QEMU does not reserve any region
on the backend memory to support label data. It is a
'label-less' NVDIMM device mode that linux will use whole
memory on the device as a single namesapce
This is useful for the u
It describes the basic concepts of NVDIMM ACPI and the interface
between QEMU and the ACPI BIOS
Signed-off-by: Xiao Guangrong
---
docs/specs/acpi_nvdimm.txt | 179 +
1 file changed, 179 insertions(+)
create mode 100644 docs/specs/acpi_nvdimm.txt
diff
Introduce "nvdimm" device which is based on dimm device type
128K memory region which is the minimum namespace label size
required by NVDIMM Namespace Spec locates at the end of
backend memory device is reserved for label data
We can use "-m 1G,maxmem=100G,slots=10 -object memory-backend-file,
id
Curretly, the memory region of backed memory is directly mapped to
guest's address space, however, it is not true for nvdimm device
This patch let dimm device realize this fact and use
DIMMDeviceClass->get_memory_region method to get the mapped memory
region
Signed-off-by: Xiao Guangrong
---
hw
This patch is generated by this script:
find ./ -name "*.[ch]" -o -name "*.json" -o -name "trace-events" -type f \
| xargs sed -i "s/PC_DIMM/DIMM/g"
find ./ -name "*.[ch]" -o -name "*.json" -o -name "trace-events" -type f \
| xargs sed -i "s/PCDIMM/DIMM/g"
find ./ -name "*.[ch]" -o -name "*.json
QEMU keeps the state of memory of dimm device during live migration,
however, it is not enough for nvdimm device as its memory does not
contain its label data, so that we should protect the whole backend
memory instead
Signed-off-by: Xiao Guangrong
---
hw/mem/dimm.c | 14 --
1 file c
nvdimm need check if the backend memory is large enough to contain label
data and init its memory region when the device is realized, so introduce
realize callback which is called after common dimm has been realize
Signed-off-by: Xiao Guangrong
---
hw/mem/dimm.c | 5 +
include/hw/mem
Rename qmp_pc_dimm_device_list.c to qmp_dimm_device_list.c
Signed-off-by: Xiao Guangrong
---
stubs/Makefile.objs | 2 +-
stubs/{qmp_pc_dimm_device_list.c => qmp_dimm_device_list.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename stubs/{qmp_pc_d
pc_existing_dimms_capacity() can be static since it is not used out of
pc-dimm.c and drop the pc_ prefix to prepare the work which abstracts
dimm device type from pc-dimm
Signed-off-by: Xiao Guangrong
---
hw/mem/pc-dimm.c | 73
include/hw/
A base device, dimm, is abstracted from pc-dimm, so that we can
build nvdimm device based on dimm in the later patch
Signed-off-by: Xiao Guangrong
---
default-configs/i386-softmmu.mak | 1 +
default-configs/ppc64-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
hw/mem/Makefile.
It's not used any more
Signed-off-by: Xiao Guangrong
---
include/hw/mem/pc-dimm.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/hw/mem/pc-dimm.h b/include/hw/mem/pc-dimm.h
index d83bf30..11a8937 100644
--- a/include/hw/mem/pc-dimm.h
+++ b/include/hw/mem/pc-dimm.h
@@ -20,8 +20,6 @@
- hostmem-file.c is compiled only if CONFIG_LINUX is enabled so that is
unnecessary to do the same check in the source file
- the interface, HostMemoryBackendClass->alloc(), is not called many
times, do not need to check if the memory-region is initialized
Signed-off-by: Xiao Guangrong
---
Currently, file_ram_alloc() only works on directory - it creates a file
under @path and do mmap on it
This patch tries to allow it to work on file directly, if @path is a
directory it works as before, otherwise it treats @path as the target
file then directly allocate memory from it
Signed-off-by
Rename:
pc-dimm.c => dimm.c
pc-dimm.h => dimm.h
It prepares the work which abstracts dimm device type for both pc-dimm and
nvdimm
Signed-off-by: Xiao Guangrong
---
hw/Makefile.objs | 2 +-
hw/acpi/ich9.c | 2 +-
hw/acpi/memory_hotplug.c
It avoid explicit Mutex and will be used by NVDIMM ACPI
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 26 --
include/hw/acpi/aml-build.h | 1 +
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
ind
Currently file_ram_alloc() is designed for hugetlbfs, however, the memory
of nvdimm can come from either raw pmem device eg, /dev/pmem, or the file
locates at DAX enabled filesystem
So this patch let it work on any kind of path
Signed-off-by: Xiao Guangrong
---
exec.c | 56 +
Implement ObjectType which is used by NVDIMM _DSM method in
later patch
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 8
include/hw/acpi/aml-build.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index efc06ab..9f792ab 1
Implement Concatenate term which is used by NVDIMM _DSM method
in later patch
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 14 ++
include/hw/acpi/aml-build.h | 1 +
2 files changed, 15 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index 9fe
Use the whole file size if @size is not specified which is useful
if we want to directly pass a file to guest
Signed-off-by: Xiao Guangrong
---
backends/hostmem-file.c | 48
1 file changed, 44 insertions(+), 4 deletions(-)
diff --git a/backends/h
There are three places use the some logic to get the page size on
the file path or file fd
This patch introduces qemu_file_get_page_size() to unify the code
Signed-off-by: Xiao Guangrong
---
include/qemu/osdep.h | 1 +
target-ppc/kvm.c | 21 +++--
util/oslib-posix.c | 16
Implement DeRefOf term which is used by NVDIMM _DSM method in later patch
Reviewed-by: Igor Mammedov
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 8
include/hw/acpi/aml-build.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-bu
This patchset can be found at:
https://github.com/xiaogr/qemu.git nvdimm-v6
It is based on pci branch on Michael's tree and the top commit is:
commit 6f96a31a06c2a1 (tests: re-enable vhost-user-test).
Changelog in v6:
- changes from Stefan's comments:
1) fix code style of struct naming by
Implement SizeOf term which is used by NVDIMM _DSM method in later patch
Reviewed-by: Igor Mammedov
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 8
include/hw/acpi/aml-build.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-bui
Implement CreateField term which is used by NVDIMM _DSM method in later patch
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 13 +
include/hw/acpi/aml-build.h | 1 +
2 files changed, 14 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index a722
On 10/10/2015 03:07 AM, Eric Blake wrote:
> On 09/25/2015 12:17 AM, Wen Congyang wrote:
>> For block replication, we have such backing chain:
>> secondary disk <-- hidden disk <-- active disk
>> secondary disk is top BDS(use bacing reference), so it can be opened in
>
> s/BDS(use bacing/BDS (u
These comments start immediately after the current longest name in the
list. Tab them out to the next tab stop to give a little breathing room
and prepare for FIXUP_BOARD_SETUP which will require more indent.
Reviewed-by: Peter Maydell
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
s/com
Add a Linux-specific pre-boot routine that matches the device-
specific bootloaders behaviour. This is needed for modern Linux that
expects the ARM PLL in SLCR to be a more even value (not 26).
Cc: Alistair Francis
Signed-off-by: Peter Crosthwaite
---
Changed since v1:
Left main loader address u
Add an API for boards to inject their own preboot software (or
firmware) sequence.
The software then returns to the bootloader via the link register. This
allows boards to do their own little bits of firmware setup without
needed to replace the bootloader completely (which is the requirement
for e
Firstly, enable monitor mode and PSCI, both are which are features of
this board.
In addition to PSCI, this board also uses SMC for cache maintainence
ops. This means we need a secure monitor to catch these and nop them.
Use the ARM boot board-setup feature to implement this. All traps to
monitor
Add a flag that when set, will cause the primary CPU to start in secure
mode, even if the overall boot in non-secure. This is useful for when
there is a board-setup blob that needs to run from secure mode, but
device and secondary CPU init should still be done as-normal for a non-
secure boot.
Sig
Hi,
This adds support for machine-specific primary boot blobs. This can be
used to install little bits of firmware or boot code without having
to throw the whole QEMU bootloader out and BYO (with device drivers
and all).
It is then used to fix two boards, Zynq and Highbank, both which have
small
On 10/28/2015 01:44 PM, Jason Wang wrote:
>
> On 10/26/2015 01:00 AM, Leonid Bloch wrote:
>> Hello qemu-devel,
>>
>> This patch series is an RFC for the new networking device emulation
>> we're developing for QEMU.
>>
>> This new device emulates the Intel 82574 GbE Controller and works
>> with un
This is the place to initialize platform specific bits of AioContext.
Signed-off-by: Fam Zheng
---
aio-posix.c | 4
aio-win32.c | 4
async.c | 13 +++--
include/block/aio.h | 8
4 files changed, 27 insertions(+), 2 deletions(-)
diff --gi
To minimize code duplication, epoll is hooked into aio-posix's
aio_poll() instead of rolling its own. This approach also has both
compile-time and run-time switchability.
1) When QEMU starts with a small number of fds in the event loop, ppoll
is used.
2) When QEMU starts with a big number of fds,
This allows AioContext users to check the enable/disable state of
external clients.
Signed-off-by: Fam Zheng
---
include/block/aio.h | 11 +++
1 file changed, 11 insertions(+)
diff --git a/include/block/aio.h b/include/block/aio.h
index bcc7d43..dcf74be 100644
--- a/include/block/aio.h
v4: Rebase onto master (with aio_disable_external):
Don't use epoll if aio_external_disabled(ctx);
Change assert on epoll_ctl return code to disable epoll;
Rerun benchmark;
v3: Remove the redundant check in aio_epoll_try_enable. [Stefan]
v2: Merge aio-epoll.c into aio-posix.c. [Paolo]
On 10/29/2015 06:27 PM, Leonid Bloch wrote:
> On Thu, Oct 29, 2015 at 12:01 PM, Jason Wang wrote:
>>
>> On 10/29/2015 05:33 PM, Leonid Bloch wrote:
>>> On Thu, Oct 29, 2015 at 5:04 AM, Jason Wang wrote:
On 10/28/2015 11:31 PM, Leonid Bloch wrote:
> These registers appear in Intel's spe
On 2015年10月30日 00:17, Alexander Duyck wrote:
> On 10/29/2015 01:33 AM, Lan Tianyu wrote:
>> On 2015年10月29日 14:58, Alexander Duyck wrote:
>>> Your code was having to do a bunch of shuffling in order to get things
>>> set up so that you could bring the interface back up. I would argue
>>> that it ma
Closing based on the assumption that a working qemu-img is available
now.
** Changed in: cinder
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qem
On 2015/10/30 2:17, Wei Huang wrote:
> On 10/29/2015 09:27 AM, Shannon Zhao wrote:
>> ACPI SPEC 5.0 defines GPIO-signaled ACPI Events for Hardware-reduced
>> platforms(like ARM). It uses GPIO pin to trigger an event to the guest.
>> For QEMU, here we add PL061 GPIO controller and use PIN 3 for
>>
Hi Yongbok,
On Tue, Oct 27, 2015 at 05:12:35PM +, Yongbok Kim wrote:
> Add part of GCR Block which Linux Kernel utilises and it is enough
> to bring the GIC up.
> It defines full 32 Kbytes address space allocated for GCR but only few
> registers are implemented such as config, revision, status
On Thu, Oct 29, 2015 at 7:41 AM, Peter Maydell wrote:
> We now have a qemu-arm mailing list for ARM patches and discussion,
> so add an L: entry for it to the various ARM related entries in
> MAINTAINERS.
>
> Signed-off-by: Peter Maydell
Looks fine to me
Reviewed-by: Alistair Francis
Thanks,
On Tue, Oct 27, 2015 at 05:12:34PM +, Yongbok Kim wrote:
> Physical base address for the memory-mapped Coherency Manager Global
> Configuration Register space.
> The MIPS default location for the GCR_BASE address is 0x1FBF_8.
> This register only exists if Config3 CMGCR is set to one.
>
> Sign
On Thu, Oct 29, 2015 at 05:17:52PM +, Yongbok Kim wrote:
> Correct updating XContext.Region field on mmu exceptions.
> If Config3.CTXTC = 0 then the R field of XContext has to be updated
> with the value of bits 63..62 of the virtual address upon a TLB
> exception.
It wouldn't hurt to mention
On 10/29/2015 12:27 PM, Markus Armbruster wrote:
>> Sounds like we have some quadratic (or worse) scaling in the parser.
>> Worth fixing some day, but I also agree that we don't have to tackle it
>> in this series.
>
> I believe it's linear with a criminally negligent constant (several KiB
> per t
On Thu, Oct 29, 2015 at 07:26:14AM +0100, Markus Armbruster wrote:
> Sam Bobroff writes:
>
> > Currently when constructing an inet socket monitor (e.g. via "-monitor
> > telent:localhost:12345,server,nowait") the port is ignored and a
> > random one is used instead. It appears this behaviour was
On Thu, Oct 29, 2015 at 12:04 PM, Peter Crosthwaite
wrote:
> On Thu, Oct 29, 2015 at 10:45 AM, Alistair Francis
> wrote:
>> On Thu, Oct 29, 2015 at 1:27 AM, Frederic Konrad
>> wrote:
>>> On 29/10/2015 03:00, Peter Crosthwaite wrote:
On Wed, Oct 28, 2015 at 10:32 AM, Alistair Francis <
On 10/29/2015 05:25 PM, Peter Maydell wrote:
> On 29 October 2015 at 21:20, Laszlo Ersek wrote:
>> On 10/29/15 21:29, John Snow wrote:
>>> Here's a good takeaway quote:
>>>
>>> 'Also, _FORTIFY_SOURCE + glibc + clang is not supported and does not
>>> work (for instance, it relies on __builtin_va_
On 29 October 2015 at 21:20, Laszlo Ersek wrote:
> On 10/29/15 21:29, John Snow wrote:
>> Here's a good takeaway quote:
>>
>> 'Also, _FORTIFY_SOURCE + glibc + clang is not supported and does not
>> work (for instance, it relies on __builtin_va_pack_len and friends,
>> which we have no intention of
Aargh, clicked "Reply" instead of "Reply All". Resending.
On 10/29/15 21:29, John Snow wrote:
>
>
> On 10/29/2015 04:22 PM, John Snow wrote:
>> Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
>> D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
>>
>> This interferes, curr
On 10/21/2015 08:51 PM, Michael Roth wrote:
Hi everyone,
The following new patches are queued for QEMU stable v2.4.1:
https://github.com/mdroth/qemu/commits/stable-2.4-staging
The release is planned for 2015-11-03:
http://wiki.qemu.org/Planning/2.4
Please respond here or CC qemu-sta...
From: Paolo Bonzini
This is a bit easier to use than "-trace" if you are also enabling
other kinds of logging. It is also more discoverable for experienced
QEMU users, and accessible from user-mode emulators.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Bornt
This series does three things:
1) add a "-trace [enable=]foo" option to enable one or more trace
events, and a "-trace help" option to show the list of tracepoints
(patches 4-5)
2) change the stderr tracing backend so that it prints to the
-D log file, and enable it by default. "-trace file=..."
From: Paolo Bonzini
Mention the ftrace backend too.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
qemu-options.hx | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 949db7f..5
log will become common facility with tracepoints support in next step.
Signed-off-by: Denis V. Lunev
Reviewed-by: Paolo Bonzini
---
Makefile.objs| 1 -
util/Makefile.objs | 1 +
qemu-log.c => util/log.c | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename qemu-log.c =>
From: Paolo Bonzini
Split the bits that require it to exec/log.h.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
bsd-user/main.c | 1 +
cpu-exec.c| 1 +
exec.c| 1 +
hw/acpi/cpu_hotpl
From: Paolo Bonzini
This enables integration with other QEMU logging facilities.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 5e65dd5..2
From: Paolo Bonzini
This is cleaner and has two advantages. First, it improves error
reporting with -daemonize. Second, multiple "-trace events" options
now cumulate.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
qemu-io.c | 2 +-
tra
From: Paolo Bonzini
This is cleaner, and improves error reporting with -daemonize.
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
qemu-io.c | 2 +-
trace/control.c | 17 -
trace/control.h | 13 -
trace/simple.
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
configure | 4 ++--
include/qemu/log.h | 1 +
scripts/tracetool/backend/{stderr.py => log.py} | 9 +
original idea to split calling locations was to spawn tracing thread
in the final child process according to
commit 8a745f2a9296ad2cf6bda33534ed298f2625a4ad
Author: Michael Mueller
Date: Mon Sep 23 16:36:54 2013 +0200
os_daemonize is now on top of both locations. Drop unneeded ifs.
From: Paolo Bonzini
Allow enabling events without going through a file, for example:
qemu-system-x86_64 -trace bdrv_aio_writev -trace bdrv_aio_readv
or with globbing too:
qemu-system-x86_64 -trace 'bdrv_aio_*'
if an appropriate backend is enabled (simple, stderr, ftrace).
Signed-off-by
From: Paolo Bonzini
Print a list of trace points
Signed-off-by: Paolo Bonzini
Signed-off-by: Denis V. Lunev
Acked-by: Christian Borntraeger
---
qemu-options.hx | 2 ++
trace/control.c | 21 -
trace/control.h | 7 +++
3 files changed, 29 insertions(+), 1 deletion(-)
On 10/29/2015 02:25 PM, Matt Gingell wrote:
> Hi,
>
> The following patch adds support for the new KVM split irqchip
> interface discussed recently on the KVM mailing list.
>
> [kvm] KVM: x86: Split the APIC from the rest of IRQCHIP.
> http://www.mailbrowse.com/kvm/138252.html
>
> Our testing fo
Hi,
The following patch adds support for the new KVM split irqchip
interface discussed recently on the KVM mailing list.
[kvm] KVM: x86: Split the APIC from the rest of IRQCHIP.
http://www.mailbrowse.com/kvm/138252.html
Our testing found some issues with the implementation of split IRQ
chip in t
Similar to the previous commit, move the detection of a collision
in enum values from parse time to QAPISchemaEnumType.check().
This happens to also detect collisions in union branch names
mapping to the same enum value, even when the names do not
collide case-wise. So for a decent error message,
Detect attempts to declare two object members that would result
in the same C member name, by keying the 'seen' dictionary off
of the C name rather than the qapi name. It also requires passing
info through some of the check() methods.
This fixes a previously-broken test, and the resulting error
m
It should be fairly obvious that qapi base classes need to
form an acyclic graph, since QMP cannot specify the same
key more than once, while base classes are included as flat
members alongside other members added by the child. But the
old check_member_clash() parser function was not prepared to
c
With the previous commit, we have two different locations for
detecting member name clashes - one at parse time, and another
at QAPISchema*.check() time. Consolidate some of the checks
into a single place, which is also in line with our TODO to
eventually move all of the parse time semantic checki
Pending prerequisite: Markus' qapi-next branch (subset B)
git://repo.or.cz/qemu/armbru.git qapi-next
https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg06417.html
Pending prerequisite: Subset C
https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg06674.html
Also available as a tag at th
Future commits will migrate semantic checking away from parsing
and over to the various QAPISchema*.check() methods. But to
report an error message about an incorrect semantic use of a
member of an object type, it helps to know which type, command,
or event owns the member. In particular, when a
On 10/29/2015 04:22 PM, John Snow wrote:
> Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
> D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
>
> This interferes, currently, with any arm target build.
>
> Work around this by disabling FORTIFY_SOURCE for clang builds
> i
Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
This interferes, currently, with any arm target build.
Work around this by disabling FORTIFY_SOURCE for clang builds
if a problem is observed.
Newer versions of clang such as
Add BANK_ #defines to index banked registers.
Suggested-by: Peter Maydell
Signed-off-by: Soren Brinkmann
---
v2:
- move #defines from cpu.h to internals.h
- drop ARM_ prefix in #defines
---
target-arm/helper.c| 37 ++---
target-arm/internals.h | 16
Quoting Denis V. Lunev (2015-10-28 10:13:54)
> This patchset is reincarnation of one patch discussed in the scope of
> QEMU 2.4 and rejected for that time. Actually we should use
> non-blocking descriptors in QGA on Windows in guest-file-open exactly
> like was done for Posix.
>
> Changes from v3:
Quoting Markus Armbruster (2015-10-22 03:01:32)
> I'm afraid
>
> 2d0583f qmp: Fix device-list-properties not to crash for abstract device
> 2874c65 qdev: Protect device-list-properties against broken devices
> 55b4efb Revert "qdev: Use qdev_get_device_class() for -device ,help"
>
> un
On 10/29/2015 12:33 PM, Markus Armbruster wrote:
>> Still doesn't build with old glib:
>>
>> In file included from /Users/pm215/src/qemu-for-merges/qga/commands.c:14:
>> In file included from
>> /Users/pm215/src/qemu-for-merges/qga/guest-agent-core.h:14:
>> In file included from
>> /Users/pm215/s
On Thu, Oct 29, 2015 at 10:45 AM, Alistair Francis
wrote:
> On Thu, Oct 29, 2015 at 1:27 AM, Frederic Konrad
> wrote:
>> On 29/10/2015 03:00, Peter Crosthwaite wrote:
>>> On Wed, Oct 28, 2015 at 10:32 AM, Alistair Francis <
>>> alistair.fran...@xilinx.com> wrote:
>>>
Connect the Xilinx SPI d
On Thu, 29 Oct 2015 17:23:43 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Thu, 29 Oct 2015 12:15:09 +0100
> > Markus Armbruster wrote:
> >
> >> Leak introduced in commit 8a4f501..710aec9, v2.4.0.
> >>
> >> Signed-off-by: Markus Armbruster
> >
> > Reviewed-by: Luiz Capitu
Peter Maydell writes:
> On 29 October 2015 at 14:32, Markus Armbruster wrote:
>> The following changes since commit 7bc8e0c967a4ef77657174d28af775691e18b4ce:
>>
>> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into
>> staging (2015-10-29 09:49:52 +)
>>
>> are available in th
Eric Blake writes:
> On 10/29/2015 06:44 AM, Markus Armbruster wrote:
>> This would have prevented the regression mentioned in the previous
>> commit.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> tests/check-qjson.c | 29 +
>> 1 file changed, 29 insertions(+)
>
Eric Blake writes:
> On 10/29/2015 06:44 AM, Markus Armbruster wrote:
>> Commit 29c75dd "json-streamer: limit the maximum recursion depth and
>> maximum token count" attempts to guard against excessive heap usage by
>> limiting total token size (it says "token count", but that's a lie).
>>
>> To
From: Cornelia Huck
Devices that are compliant with virtio-1 do not support scsi
passthrough any more (and it has not been a recommended setup
anyway for quite some time). To avoid having to switch it off
explicitly in newer qemus that turn on virtio-1 by default, let's
switch the default to scsi
On 10/29/2015 09:27 AM, Shannon Zhao wrote:
> ACPI SPEC 5.0 defines GPIO-signaled ACPI Events for Hardware-reduced
> platforms(like ARM). It uses GPIO pin to trigger an event to the guest.
> For QEMU, here we add PL061 GPIO controller and use PIN 3 for
> system_powerdown, reserving PIN 0, 1, 2 for
(CCing Michal and libvir-list, so libvirt team is aware of this
restriction)
On Thu, Oct 29, 2015 at 02:36:37PM +0100, Igor Mammedov wrote:
> On Tue, 27 Oct 2015 14:36:35 -0200
> Eduardo Habkost wrote:
>
> > On Tue, Oct 27, 2015 at 10:14:56AM +0100, Igor Mammedov wrote:
> > > On Tue, 27 Oct 2015
On Thu, Oct 29, 2015 at 10:45 AM, Alistair Francis
wrote:
> On Thu, Oct 29, 2015 at 1:27 AM, Frederic Konrad
> wrote:
>> On 29/10/2015 03:00, Peter Crosthwaite wrote:
>>> On Wed, Oct 28, 2015 at 10:32 AM, Alistair Francis <
>>> alistair.fran...@xilinx.com> wrote:
>>>
Connect the Xilinx SPI d
From: Sai Pavan Boddu
Add two SYSBUS_SDHCI devices for xlnx-zynqmp
Signed-off-by: Sai Pavan Boddu
Reviewed-by: Peter Crosthwaite
Signed-off-by: Stefan Hajnoczi
---
hw/arm/xlnx-zynqmp.c | 28
include/hw/arm/xlnx-zynqmp.h | 3 +++
2 files changed, 31 inser
From: Kevin Wolf
The function manually recursed into bs->file and bs->backing to check
whether there were any requests pending, but it ignored other children.
There's no need to special case file and backing here, so just replace
these two explicit recursions by a loop recursing for all child no
1 - 100 of 288 matches
Mail list logo
