>> I see one thing: symlinks somewhere in the path (which seemed to be the
>> reason introducing the *at family). But I think that this can be handled
>> by canonlizing the path, too. realpath should do the job quite well.
>>
>
> Unfortunately now because we have TOCTOU condition here: some path
SLOF receives a device tree and updates it with various properties
before switching to the guest kernel and QEMU is not aware of any changes
made by SLOF. Since there is no real RTAS and QEMU implements it,
it makes sense to pass the SLOF device tree to QEMU so the latter could
implement RTAS
On Wed, 2017-10-11 at 09:28 +0200, Cédric Le Goater wrote:
> On 10/11/2017 05:49 AM, Andrew Jeffery wrote:
> > On Tue, 2017-10-10 at 15:30 +0200, Cédric Le Goater wrote:
> > > On 10/09/2017 02:04 AM, Andrew Jeffery wrote:
> > > > On Wed, 2017-09-20 at 09:01 +0200, Cédric Le Goater wrote:
> > > > >
** Description changed:
Distribution: Arch Linux, Kernel: linux-4.13.5, Qemu: 2.10.1, OVMF: git
(built 06.10.17).
Steps to reproduce: create Qemu VM with such config:
QEMU_VM_NAME=$(basename $(dirname "$0")) #Qemu virtual machine name (taken
from working directory)
On Sat, 14 Oct 2017 20:33:37 +1100
David Gibson wrote:
> On Fri, Oct 13, 2017 at 01:31:44PM +0200, Greg Kurz wrote:
> > The current code assumes that only the CPU core object holds a
> > reference on each individual CPU object, and happily frees their
> > allocated
On 15.10.2017 21:50, Greg Kurz wrote:
>> Hi again,
>>
>> I see one thing: symlinks somewhere in the path (which seemed to be the
>> reason introducing the *at family). But I think that this can be handled
>> by canonlizing the path, too. realpath should do the job quite well.
>>
>
>
On Sun, 15 Oct 2017 21:13:34 +0200
"Michael Fritscher" wrote:
> >
> > Hi,
> >
> > dumb question: what is the advantage of openat vs. open - only the thing
> > that someone doesn't need to build the path together by hand?
> >
> > If I understand the man page of openat
On Sun, 15 Oct 2017 21:02:56 +0200
"Michael Fritscher" wrote:
> > On 29/09/2017 16:14, Michael Fritscher wrote:
> >>> Yes, that's pretty much the only way to do it; it's not the easiest
> >>> thing because you have to use NT kernel APIs (NtCreateFile) rather than
> >>>
>
> Hi,
>
> dumb question: what is the advantage of openat vs. open - only the thing
> that someone doesn't need to build the path together by hand?
>
> If I understand the man page of openat correctly, it does _not_ prevent
> someone to break out of the jail by using e.g. ../../../blah .
> If
> On 29/09/2017 16:14, Michael Fritscher wrote:
>>> Yes, that's pretty much the only way to do it; it's not the easiest
>>> thing because you have to use NT kernel APIs (NtCreateFile) rather than
>>> e.g. CreateFile. Likewise for NtQueryAttributesFile,
>>> NtQueryDirectoryObject, etc.
Many thanks Peter
On Sun, Oct 15, 2017 at 6:50 PM, Peter Maydell
wrote:
> On 15 October 2017 at 17:47, Ramy Sameh wrote:
> > I was tracking the calling of function pl011_read, and I noticed that it
> is
> > called from function
Reduce latency when playing back via Pulse Audio, by removing the
separate threads that feed PA. These are not needed, since feeding
can be done in a non blocking way directly from the audio timer.
This also exposes several new configuration settings that make it
easier for the user to tune the
Currently, the HDA device tries to sync itself with the QEMU audio
backend by waiting for the guest driver to handle buffer completion
interrupts. This causes the backend to often read too much data from the
device, as well as running out of data whenever the guest takes too long
to handle the
Motivation for this:
After being annoyed for too long with the crackling QEMU produces, I decided
to dive in and try to fix this.
This has already been tested by several people, please see the corresponding
Reddit-thread:
On 10/13/2017 09:24 AM, Alex Bennée wrote:
> Half-precision helpers for float16 maths. I didn't bother hand-coding
> the count leading zeros as we could always fall-back to host-utils if
> we needed to.
>
> Signed-off-by: Alex Bennée
> ---
> fpu/softfloat-macros.h | 39
Am 15.10.2017 um 19:46 schrieb Stefan Weil:
> Am 15.10.2017 um 17:32 schrieb Paolo Bonzini:
>> On 14/10/2017 18:53, Philippe Mathieu-Daudé wrote:
@@ -328,7 +328,7 @@ static void *do_touch_pages(void *arg)
* don't need to write at all so we don't cause
*
Am 15.10.2017 um 17:32 schrieb Paolo Bonzini:
> On 14/10/2017 18:53, Philippe Mathieu-Daudé wrote:
>>> @@ -328,7 +328,7 @@ static void *do_touch_pages(void *arg)
>>> * don't need to write at all so we don't cause
>>> * wear on the storage backing the region...
>>>
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20171015165858.19937-1-mar...@schrodt.org
Subject: [Qemu-devel] [PATCH v3 0/2] Improve audio output quality
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git
Currently, the HDA device tries to sync itself with the QEMU audio
backend by waiting for the guest driver to handle buffer completion
interrupts. This causes the backend to often read too much data from the
device, as well as running out of data whenever the guest takes too long
to handle the
v3 because I committed some whitespace only changes in v2. Sorry.
Motivation for this:
After being annoyed for too long with the crackling QEMU produces, I decided
to dive in and try to fix this.
This has already been tested by several people, please see the corresponding
Reddit-thread:
Reduce latency when playing back via Pulse Audio, by removing the
separate threads that feed PA. These are not needed, since feeding
can be done in a non blocking way directly from the audio timer.
This also exposes several new configuration settings that make it
easier for the user to tune the
On 13 October 2017 at 17:24, Alex Bennée wrote:
> Mention the pseudo-code fragment from which this is based and correct
> the spelling of signalling.
We are following the IEEE spec here, which spells it "signaling"
with one 'l', being American. (The ARM ARM also uses the
On 15 October 2017 at 17:47, Ramy Sameh wrote:
> I was tracking the calling of function pl011_read, and I noticed that it is
> called from function *memory_region_read_accessor *in memory.c
>
> I also noticed that all peripherals reading functions (e.g. pl050_read,
>
On 13 October 2017 at 17:36, Stefan Berger wrote:
> This is NOT test code. It's determining whether the external TPM is a TPM
> 1.2 or TPM 2 emulation. This avoids having to start QEMU with a '--tpm2'
> parmeter equivalent as well as the external emulator. Passing this
On 15 October 2017 at 17:30, Lluís Vilanova wrote:
> Thinking about it, shouldn't this always be the same given QEMU's TLB/page
> table
> consistency assurances?
What TLB/page table consistency assurances? For ARM at least
we will only update (ie flush) the TLB when the
Hello all,
I was tracking the calling of function pl011_read, and I noticed that it is
called from function *memory_region_read_accessor *in memory.c
I also noticed that all peripherals reading functions (e.g. pl050_read,
pl190_read ... etc) in the emulated VersatilePB board, are called from the
Emilio G Cota writes:
> On Fri, Oct 06, 2017 at 18:07:16 +0300, Lluís Vilanova wrote:
>> Emilio G Cota writes:
>> > On Thu, Oct 05, 2017 at 02:28:12 +0300, Lluís Vilanova wrote:
>> >> The API takes care of telling you if the access could be performed
>> >> successfully. If you access the
Reduce latency when playing back via Pulse Audio, by removing the
separate threads that feed PA. These are not needed, since feeding
can be done in a non blocking way directly from the audio timer.
This also exposes several new configuration settings that make it
easier for the user to tune the
After being annoyed for too long with the crackling QEMU produces, I decided
to dive in and try to fix this.
This has already been tested by several people, please see the corresponding
Reddit-thread:
https://www.reddit.com/r/VFIO/comments/74vokw/improved_pulse_audio_driver_for_qemu/
I
Currently, the HDA device tries to sync itself with the QEMU audio
backend by waiting for the guest driver to handle buffer completion
interrupts. This causes the backend to often read too much data from the
device, as well as running out of data whenever the guest takes too long
to handle the
On 10/13/2017 09:24 AM, Alex Bennée wrote:
> We do implement all the opcodes.
>
> Signed-off-by: Alex Bennée
> ---
> target/arm/translate-a64.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Reviewed-by: Richard Henderson
r~
On 10/13/2017 09:24 AM, Alex Bennée wrote:
> Mention the pseudo-code fragment from which this is based and correct
> the spelling of signalling.
>
> Signed-off-by: Alex Bennée
> ---
> fpu/softfloat-specialize.h | 10 +-
> 1 file changed, 5 insertions(+), 5
On 10/13/2017 09:24 AM, Alex Bennée wrote:
> -if (float ## s ## _is_quiet_nan(a, status) && \
> +if (float ## s ## _is_signaling_nan(a, status) || \
> +float ## s ## _is_signaling_nan(b, status)) { \
> +
On 15/10/2017 16:01, Michal Suchánek wrote:
>>> ./configure --disable-gtk --disable-sdl --disable-opengl
>> You can also use the runtime -display options (assuming
>> your development environment has the libraries
>> and your runtime environment has them installed, there's
>> no harm in having a
On 14/10/2017 18:53, Philippe Mathieu-Daudé wrote:
>> @@ -328,7 +328,7 @@ static void *do_touch_pages(void *arg)
>> * don't need to write at all so we don't cause
>> * wear on the storage backing the region...
>> */
>> -*(volatile char *)addr =
On Fri, 13 Oct 2017 17:08:49 +0100
Peter Maydell wrote:
> On 13 October 2017 at 08:00, Gerd Hoffmann wrote:
> > On Thu, 2017-10-12 at 16:25 -0400, hanji unit wrote:
> >> Hello, is it possible to run (or rebuild modifying build flags)
> >> QEMU
On 2017-10-15 23:24, Yan Vugenfirer wrote:
On 15 Oct 2017, at 15:21, ge...@hostfission.com wrote:
Hi Yan,
Thank you for the information. I am rather new to Windows Driver
development and learning as I go, so this may take some time, but
since the driver only needs to perform very basic
> On 15 Oct 2017, at 15:21, ge...@hostfission.com wrote:
>
> Hi Yan,
>
> Thank you for the information. I am rather new to Windows Driver development
> and learning as I go, so this may take some time, but since the driver only
> needs to perform very basic functions I do not see this as
Hi Yan,
Thank you for the information. I am rather new to Windows Driver
development and learning as I go, so this may take some time, but since
the driver only needs to perform very basic functions I do not see this
as being too much of a challenge.
-Geoff
On 2017-10-15 22:14, Yan
Public bug reported:
Distribution: Arch Linux, Kernel: linux-4.13.5, Qemu: 2.10.1, OVMF: git (built
06.10.17).
Steps to reproduce: create Qemu VM with such config:
QEMU_VM_NAME=$(basename $(dirname "$0")) #Qemu virtual machine name (taken from
working directory)
QEMU_WORKING_DIR="$(dirname
On Sun, 8 Oct 2017, BALATON Zoltan wrote:
I'm still trying to debug a crash that I don't understand why is
happening and how to debug it further. Any hints are apreciated. I've
described the problem previously in
http://lists.nongnu.org/archive/html/qemu-ppc/2017-08/msg00249.html
but I've dug
He Geoff,
The official virtio-win drivers upstream repository is here:
https://github.com/virtio-win/kvm-guest-drivers-windows
1. There is no ivshmem Windows Driver for now as far as I know
2. We are signing the drivers for community usage
https://fedoraproject.org/wiki/Windows_Virtio_Drivers
Hi All,
I am writing some code that needs to share a block of ram between a
Windows guest and Linux host. For this I am using the ivshmem device and
I have written a very primitive driver for windows that allows a single
application to request to memory map the pci bar (shared memory) into
Commit 8d93297 introduced a bug whereby non-inbuilt NICs are realized before
setting the default MAC address causing an assert. Switch NIC creation
over from pci_create_simple() to pci_create() which works exactly the
same except omitting the realize as originally intended.
Signed-off-by: Mark
On Sun, Oct 15, 2017 at 03:24:52PM +1100, Alexey Kardashevskiy wrote:
> This moves pci_dev->name initialization earlier so
> pci_dev->bus_master_as could get a name instead of an empty string.
Or use "name" instead of "pci_dev->name" when do address_space_init()?
But I think this one works too.
On 14/10/17 20:23, no-re...@patchew.org wrote:
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Type: series
> Message-id: 1508006342-5304-1-git-send-email-mark.cave-ayl...@ilande.co.uk
> Subject: [Qemu-devel] [PATCHv3 00/13] sun4m:
46 matches
Mail list logo