Re: [Qemu-devel] [PATCH 0/4] target-i386: Don't try to enable unsupported TCG features by default

On 11/09/2015 21:58, Eduardo Habkost wrote: > About implementing DE in TCG: I really don't think it is easier, but if > somebody wants to implement it, it would be welcome. Actually I agree that it's easier, and even a partial implementation (e.g. no I/O port breakpoints) would be nice to have

[Qemu-devel] [RFC PATCH 3/3] acpi: arm: add fw_cfg device node to dsdt

Add a fw_cfg device node to the ACPI DSDT. This is mostly informational, as the authoritative fw_cfg MMIO region(s) are listed in the Device Tree. However, since we are building ACPI tables, we might as well be thorough while at it... Signed-off-by: Gabriel Somlo --- I used

[Qemu-devel] [RFC PATCH 0/3] adding acpi node for fw_cfg on pc and arm

This series adds a fw_cfg device node to the SSDT (on pc), or to the DSDT (on arm). - Patch 1/3 moves (and renames) the BIOS_CFG_IOPORT (0x510) define from pc.c to pc.h, so that it could be used from acpi-build.c in patch 2/3. - Patch 2/3 adds a fw_cfg node to

Re: [Qemu-devel] [PATCH] pulseaudio: reduce 24s recording latency

Am 12.09.2015 um 16:35 schrieb Kővágó Zoltán: 2015-09-12 13:23 keltezéssel, Volker Rümelin írta: On start up qemu opens a connection to pulseaudio in function qpa_init_in and pulseaudio immediately starts recording to the 4MB ringbuffer. The qemu guest, Windows 8.1 in my case, doesn't consume

[Qemu-devel] [PATCH v2] hw/misc/zynq_slcr: Change CPU clock rate for Linux boots

The Linux kernel only accepts 34 Khz and 67 Khz clock rates, and may crash if the actual clock rate is too low. The clock rate used to be (ps-clk-frequency * 26 / 4), which resulted in a CPU frequency of 21 Khz if ps-clk-frequency was set to Hz. Change it to (ps-clk-frequency

Re: [Qemu-devel] [PATCH] MAINTAINERS: Add "Error reporting" entry

On Sat, Sep 12, 2015 at 4:29 AM, Markus Armbruster wrote: > Error reporting work has been flowing through my tree for a while. > Time for MAINTAINERS to catch up. > > Signed-off-by: Markus Armbruster Reviewed-by: Peter Crosthwaite

[Qemu-devel] [RFC PATCH 2/3] acpi: pc: add fw_cfg device node to ssdt

Add a fw_cfg device node to the ACPI SSDT. While the guest-side BIOS can't utilize this information (since it has to access the hard-coded fw_cfg device to extract ACPI tables to begin with), having fw_cfg listed in ACPI will help the guest kernel keep a more accurate inventory of in-use IO port

[Qemu-devel] [RFC PATCH 1/3] pc: fw_cfg: move ioport base constant to pc.h

Move BIOS_CFG_IOPORT define from pc.c to pc.h, and rename it to FW_CFG_IO_BASE. Also, add FW_CFG_IO_SIZE define (set to 0x02, to cover the overlapping 16-bit control and 8-bit data ports). Signed-off-by: Gabriel Somlo --- hw/i386/pc.c | 5 ++--- include/hw/i386/pc.h | 3

[Qemu-devel] [PATCH v3 1/1] intel_iommu: Add support for translation for devices behind bridges

- Use a hash table indexed on bus pointers to store information about buses instead of using the bus numbers. Bus pointers are stored in a new VTDBus struct together with the vector of device address space pointers indexed by devfn. - The bus number is still used for lookup for selective SID

[Qemu-devel] [PATCH v3 0/1] intel_iommu: Add support for translation for devices behind bridges

This patch set has been completely reimplemented according to ideas from the discussion of v2. It still solves the same problem, but does so only within the Intel IOMMU code and Q35, without changing the IOMMU interface. This eliminates the need for any separate interface change patch. This is

Re: [Qemu-devel] [PATCH v2 0/2] intel_iommu: Add support for translation for devices behind bridges

On Thu, 2015-09-03 at 07:26 +0200, Knut Omang wrote: > On Thu, 2015-09-03 at 08:33 +1000, Benjamin Herrenschmidt wrote: > > On Wed, 2015-09-02 at 10:12 -0600, Alex Williamson wrote: > > > > > There are very specific rules for translating requester IDs across > > > bridges. Bus numbers can change

Re: [Qemu-devel] [PATCH] linux-user/signal.c: Use setup_rt_frame() instead of setup_frame() for target openrisc

On 9/13/15 00:23, Peter Maydell wrote: > On 12 September 2015 at 16:32, wrote: >> From: Chen Gang >> >> qemu has already considered about some targets may have no traditional >> signals. And openrisc's setup_frame() is dummy, but it can be

Re: [Qemu-devel] [PATCH] linux-user/signal.c: Use setup_rt_frame() instead of setup_frame() for target openrisc

On 12 September 2015 at 16:32, wrote: > From: Chen Gang > > qemu has already considered about some targets may have no traditional > signals. And openrisc's setup_frame() is dummy, but it can be supported > by setup_rt_frame(). > >

[Qemu-devel] [PATCH v2] hw/misc: Add support for ADC controller in Xilinx Zynq 7000

Add support for the Xilinx XADC core used in Zynq 7000. References: - Zynq-7000 All Programmable SoC Technical Reference Manual - 7 Series FPGAs and Zynq-7000 All Programmable SoC XADC Dual 12-Bit 1 MSPS Analog-to-Digital Converter Tested with Linux using qemu machine xilinx-zynq-a9 with

Re: [Qemu-devel] [PATCH v2 0/2] intel_iommu: Add support for translation for devices behind bridges

On Sat, 2015-09-12 at 20:37 +0200, Knut Omang wrote: > As the thread went silent after our conclusions, I have made a second > implementation for the Intel IOMMU according to this alternate scheme, > It keeps the current API and handles the bus number resolution lazily > within the IOMMU

[Qemu-devel] [PATCH] linux-user/signal.c: Skip calling unlock_user_struct() when lock_user_struct() failed for target ppc and ppc64

From: Chen Gang For target ppc and ppc64, all related funcitons have this issue. Signed-off-by: Chen Gang --- linux-user/signal.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/linux-user/signal.c

[Qemu-devel] Python problem

After a 'git pull' on 9/12/2015, I noticed that QEMU no longer builds on Mac OS 10.6. I think there is a problem with a python script. This is the error message: GEN qmp-commands.h Traceback (most recent call last): File "/scripts/qapi-commands.py", line 352, in ret =

Re: [Qemu-devel] Python problem

On Sep 12, 2015, at 10:04 PM, Eric Blake wrote: > On 09/12/2015 07:57 PM, Programmingkid wrote: >> After a 'git pull' on 9/12/2015, I noticed that QEMU no longer builds on Mac >> OS 10.6. I think there is a problem with a python script. This is the error >> message: >> >> GEN

[Qemu-devel] [PATCH] linux-user/signal.c: Skip calling unlock_user_struct() when lock_user_struct() failed for target m68k

From: Chen Gang For target m68k, setup_rt_frame() and do_rt_sigreturn() have this issue. Signed-off-by: Chen Gang --- linux-user/signal.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/linux-user/signal.c

[Qemu-devel] ping: [PATCH v5] raw-posix.c: Make physical devices usable in QEMU under Mac OS X host

> Mac OS X can be picky when it comes to allowing the user to use physical > devices > in QEMU. Most mounted volumes appear to be off limits to QEMU. If an issue is > detected, a message is displayed showing the user how to unmount a volume. > > Signed-off-by: John Arbuckle

Re: [Qemu-devel] Confused by QOM: /machine/unattached/device[5]/dr-connector[255]/fdt

On 09/09/2015 10:16 AM, Paolo Bonzini wrote: >>> Is returning NULL without setting an error okay? >>> >>> Should it return qnull() instead? Then the QMP return value would be >>> JSON null. > > JSON null support in QObject is new, it should be the result of > object_property_get_qobject() or

Re: [Qemu-devel] Python problem

On 09/12/2015 07:57 PM, Programmingkid wrote: > After a 'git pull' on 9/12/2015, I noticed that QEMU no longer builds on Mac > OS 10.6. I think there is a problem with a python script. This is the error > message: > > GEN qmp-commands.h > Traceback (most recent call last): > File

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

Eric Blake writes: > On 09/11/2015 02:43 PM, Eric Blake wrote: > >>> +++ b/tests/test-qmp-output-visitor.c >>> @@ -485,7 +485,7 @@ static void >>> test_visitor_out_empty(TestOutputVisitorData *data, >>> QObject *arg; >>> >>> arg =

Re: [Qemu-devel] [RFC 2/4] hw/i386: Introduce AMD IOMMU

Hi David, On 07.09.2015 17:46, Valentine Sinitsyn wrote: ...snip... +/* TODO : Mark addresses as Accessed and Dirty */ +static void amd_iommu_do_translate(AMDIOMMUAddressSpace *as, hwaddr addr, bool is_write, IOMMUTLBEntry *ret) +{ +AMDIOMMUState *s = as->iommu_state; + +int present; +

Re: [Qemu-devel] [PATCH] pulseaudio: reduce 24s recording latency

Hi, Am 12.09.2015 um 01:22 schrieb Marc-André Lureau: Current code doesn't provide pulseaudio buffer attributes for recording. Without buffer attributes pulseaudio uses a default buffer of 4MB. 4MB is approximately 24s 16bit stereo audio data at 44.1kHz. Why isn't the buffer processed as soon

Re: [Qemu-devel] [PATCH v2] error: only prepend timestamp on stderr

Stefan Hajnoczi writes: > The -msg timestamp=on option prepends a timestamp to error messages. > This is useful on stderr where it allows users to identify when an error > was raised. > > Timestamps do not make sense on the monitor since error_report() is > called in

[Qemu-devel] [PATCH] MAINTAINERS: Add "Error reporting" entry

Error reporting work has been flowing through my tree for a while. Time for MAINTAINERS to catch up. Signed-off-by: Markus Armbruster --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 688979b..54971a7 100644 ---

[Qemu-devel] [PATCH] linux-user/signal.c: Use setup_rt_frame() instead of setup_frame() for target openrisc

From: Chen Gang qemu has already considered about some targets may have no traditional signals. And openrisc's setup_frame() is dummy, but it can be supported by setup_rt_frame(). Signed-off-by: Chen Gang --- linux-user/signal.c | 9

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

On 09/12/2015 07:42 AM, Eric Blake wrote: > It looks like the stack is actually tracking two things at once: the > oldest member of the stack (qmp_output_first(), or QTAILQ_LAST) is the > root (can be any QObject), and all other members of the stack hold any > open-ended container QObject

[Qemu-devel] Invitation: Dr Velano @ Wed Sep 16, 2015 19:50 - 20:50 (shlomopongr...@gmail.com)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20150916T165000Z DTEND:20150916T175000Z DTSTAMP:20150912T140307Z ORGANIZER;CN=Shlomo Pongratz:mailto:shlomopongr...@gmail.com

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

Eric Blake writes: > On 09/12/2015 02:10 AM, Markus Armbruster wrote: > >> Relatively harmless, because the qnull_ singleton is static. Worth >> fixing anyway, of course. >> I'm still investigating, and may be able to find the patch >>> >>> Squash this in, and you can

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

On 09/12/2015 08:11 AM, Markus Armbruster wrote: >> Indeed. Without reading further, we're both shooting in the dark for >> something that makes tests pass, but without being a clean interface. >> >> How about this: go ahead with your series as proposed, with the squash >> hunk to tests/ to avoid

Re: [Qemu-devel] [PATCH] pulseaudio: reduce 24s recording latency

2015-09-12 13:23 keltezéssel, Volker Rümelin írta: Hi, Am 12.09.2015 um 01:22 schrieb Marc-André Lureau: Current code doesn't provide pulseaudio buffer attributes for recording. Without buffer attributes pulseaudio uses a default buffer of 4MB. 4MB is approximately 24s 16bit stereo audio data

Re: [Qemu-devel] [PATCH 04/29] Introduce QDict

On Sep 12, 2015, at 12:10 AM, Luiz Capitulino wrote: > On Fri, 11 Sep 2015 20:22:38 -0400 > Programmingkid wrote: > >> Could you make a tutorial on how to use the QDict type? > > There are several examples in tests/check-qdict.c. I was hoping for something with a

Re: [Qemu-devel] [PATCH] pulseaudio: reduce 24s recording latency

Hi On Fri, Sep 11, 2015 at 9:03 PM, Volker Rümelin wrote: > Current code doesn't provide pulseaudio buffer attributes for > recording. Without buffer attributes pulseaudio uses a default > buffer of 4MB. 4MB is approximately 24s 16bit stereo audio > data at 44.1kHz. > > This

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

On 09/12/2015 02:10 AM, Markus Armbruster wrote: > Relatively harmless, because the qnull_ singleton is static. Worth > fixing anyway, of course. > >>> I'm still investigating, and may be able to find the patch >> >> Squash this in, and you can have: >> Reviewed-by: Eric Blake

Re: [Qemu-devel] [PATCH] MAINTAINERS: Add "Error reporting" entry

On 09/12/2015 05:29 AM, Markus Armbruster wrote: > Error reporting work has been flowing through my tree for a while. > Time for MAINTAINERS to catch up. > > Signed-off-by: Markus Armbruster > --- > MAINTAINERS | 8 > 1 file changed, 8 insertions(+) Reviewed-by:

Re: [Qemu-devel] [PATCH v3 2/3] pci: Update pci_regs header

On Thu, 2015-09-10 at 22:27 +0200, Knut Omang wrote: > On Thu, 2015-09-10 at 21:11 +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 01, 2015 at 05:59:49PM +0200, Knut Omang wrote: > > > Pull new version from kernel v4.1 > > > > Paolo sent what I consider a better version. So looking at the

[Qemu-devel] [PATCH v4 2/3] pci: Update pci_regs header

Merge in new definitions from kernel v4.2 Adds definition necessary to support emulated SR/IOV. Signed-off-by: Knut Omang --- include/standard-headers/linux/pci_regs.h | 142 +- 1 file changed, 118 insertions(+), 24 deletions(-) diff --git

[Qemu-devel] [PATCH v4 0/3] pcie: Add support for Single Root I/O Virtualization

This patch set implements generic support for SR/IOV as an extension to the core PCIe functionality, similar to the way other capabilities such as AER is implemented. There is no implementation of any device that provides SR/IOV support included, but I have implemented a test example which can be

[Qemu-devel] [PATCH v4 1/3] pci: Make use of the devfn property when registering new devices

Without this, the devfn argument to pci_create_*() does not affect the assigned devfn. Needed to support (VF_STRIDE,VF_OFFSET) values other than (1,1) for SR/IOV. Signed-off-by: Knut Omang --- hw/pci/pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Qemu-devel] [PATCH v4 3/3] pcie: Add support for Single Root I/O Virtualization (SR/IOV)

This patch provides the building blocks for creating an SR/IOV PCIe Extended Capability header and register/unregister SR/IOV Virtual Functions. Signed-off-by: Knut Omang --- hw/pci/Makefile.objs| 2 +- hw/pci/pci.c| 99

Re: [Qemu-devel] [PATCH v6 20/26] qapi: Fix output visitor to return qnull() instead of NULL

On 09/12/2015 06:16 AM, Eric Blake wrote: >> >> where e = QTAILQ_LAST(>stack, QStack) >> >> Questions: >> >> * How can e become NULL? >> >> The only place that pushes onto >stack appears to be >> qmp_output_push_obj(). Can obviously push e with !e->value, but can't >> push null e. > > My