http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7f13420ec000ad7644b65e
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1402802
Title:
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1370585
Title:
qemu-img cannot create fixed vhdx
Status in QEMU:
Fix Released
Bug
On Tue, Jun 21, 2016 at 01:40:42AM -0400, Jeff Cody wrote:
> This update should preserve git history, and allow seamless switching
> over to the official openbios git repo, rather than pulling from the
> svn mirror. All prior history from the svn repository should still be
> preserved (i.e.,
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1357440
Title:
qemu-img: Assert for 'amend' command and the fuzzed image
Status in
This update should preserve git history, and allow seamless switching
over to the official openbios git repo, rather than pulling from the
svn mirror. All prior history from the svn repository should still be
preserved (i.e., commit hashes are the same for historical commits).
In the
On Sat, Jun 18, 2016 at 02:04:06PM +0530, Bharata B Rao wrote:
> Compat CPU type is typically specified on -cpu cmdline option like:
> -cpu host,compat=power7 or -cpu POWER8E,compat=power7 etc.
> With the introduction of sPAPR CPU core devices, we need to support
> the same for core devices too.
>
On 06/20/2016 05:39 PM, Eric Blake wrote:
> We have max_transfer documented in BlockLimits, but while we
> honor it during pwrite_zeroes, we were blindly ignoring it
> during pwritev and preadv, leading to multiple drivers having
> to implement fragmentation themselves. This series moves
>
On Sat, Jun 18, 2016 at 04:42:05PM -0400, Ido Yariv wrote:
> The current code creates a whole page mmio region for the MSI-X table
> size.
>
> However, the page containing the MSI-X table may contain other registers
> not related to MSI-X. Creating an mmio region for the whole page masks
> such
On Tue, 21 Jun 2016 02:15:23 +0200
Laszlo Ersek wrote:
> On 06/21/16 00:04, Alex Williamson wrote:
> > The kernel currently exposes the SR-IOV capability as read-only
> > through vfio-pci. This is sufficient to protect the host kernel, but
> > has the potential to confuse
On Mon, 2016-06-20 at 14:57 +0100, Peter Maydell wrote:
> On 20 June 2016 at 04:44, Andrew Jeffery wrote:
> >
> > On Fri, 2016-06-17 at 15:22 +0100, Peter Maydell wrote:
> > >
> > > +static Property aspeed_scu_properties[] = {
> > > +DEFINE_PROP_ARRAY("reset",
Now that the block layer honors max_request, we don't need to
bother with an EINVAL on overlarge requests, but can instead
assert that requests are well-behaved.
Signed-off-by: Eric Blake
---
block/iscsi.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
On Tue, 21 Jun 2016 10:16:25 +0800
Zhou Jie wrote:
> Hi, Alex
>
> > I was really hoping to hear your opinion, or at least some further
> > discussion of pros and cons rather than simply parroting back my idea.
> I understand.
>
> > My current thinking is that a
Hi, Alex
I was really hoping to hear your opinion, or at least some further
discussion of pros and cons rather than simply parroting back my idea.
I understand.
My current thinking is that a resume notifier to userspace is poorly
defined, it's not clear what the user can and cannot do
On 2016年06月20日 23:09, Peter Maydell wrote:
On 20 June 2016 at 15:55, Paolo Bonzini wrote:
On 18/06/2016 09:54, Ashijeet Acharya wrote:
Use socket_*() functions from include/qemu/sockets.h instead of
listen()/bind()/ connect()/parse_host_port(). socket_*() fucntions are
On 2016年06月21日 01:53, David Vrabel wrote:
Commit 9d29cdeaaca3a0383af764000b71492c4fc67c6e (rtl8139: port
TallyCounters to vmstate) introduced in incompatibility in the v4
format as it omitted the RxOkMul counter.
There are presumably no users that were impacted by the v4 to v4'
breakage, so
> It would be nice to at least see the patches. :)
>
> I think a lightweight q35 platform that can run the usual firmware could
> be acceptable in QEMU.
OK, I will send out v2.
>
> >> 2) this:
> >>
> >>> - it loads guest kernel directly, no BIOS, no bootloader, no realmode
> >>> code;
> >>
>
On 06/21/2016 12:45 AM, Eric Blake wrote:
On 06/20/2016 02:23 AM, Zhang Chen wrote:
Subject line is too long, missing a 'topic:' prefix, and has a typo
(souce). Suggest:
qemu-char: Fix context for g_source_attach()
OK~~ I will fix it in next version.
We want to poll and handle chardev
On Mon, 06/20 20:36, Stefan Hajnoczi wrote:
> Attempting to cancel a dma_blk_io() request causes an abort(3):
>
> void bdrv_aio_cancel(BlockAIOCB *acb)
> {
> ...
> while (acb->refcnt > 1) {
> if (acb->aiocb_info->get_aio_context) {
>
New VFIO_SPAPR_TCE_v2_IOMMU type supports dynamic DMA window management.
This adds ability to VFIO common code to dynamically allocate/remove
DMA windows in the host kernel when new VFIO container is added/removed.
This adds a helper to vfio_listener_region_add which makes
This adds support for Dynamic DMA Windows (DDW) option defined by
the SPAPR specification which allows to have additional DMA window(s)
The "ddw" property is enabled by default on a PHB but for compatibility
the pseries-2.6 machine and older disable it.
This also creates a single DMA window for
This makes use of the new "memory registering" feature. The idea is
to provide the userspace ability to notify the host kernel about pages
which are going to be used for DMA. Having this information, the host
kernel can pin them all once per user process, do locked pages
accounting (once) and not
There are going to be multiple IOMMUs per a container. This moves
the single host IOMMU parameter set to a list of VFIOHostDMAWindow.
This should cause no behavioral change and will be used later by
the SPAPR TCE IOMMU v2 which will also add a vfio_host_win_del() helper.
Signed-off-by: Alexey
Every IOMMU has some granularity which MemoryRegionIOMMUOps::translate
uses when translating, however this information is not available outside
the translate context for various checks.
This adds a get_min_page_size callback to MemoryRegionIOMMUOps and
a wrapper for it so IOMMU users (such as
Each Partitionable Endpoint (IOMMU group) has an address range on a PCI bus
where devices are allowed to do DMA. These ranges are called DMA windows.
By default, there is a single DMA window, 1 or 2GB big, mapped at zero
on a PCI bus.
PAPR defines a DDW RTAS API which allows pseries guests
On Thu, Jun 9, 2016 at 12:03 PM, Peter Maydell wrote:
> On 12 May 2016 at 23:45, Alistair Francis wrote:
>> Add memory io handlers that glue the register API to the memory API.
>> Just translation functions at this stage. Although it does
On 06/21/16 00:04, Alex Williamson wrote:
> The kernel currently exposes the SR-IOV capability as read-only
> through vfio-pci. This is sufficient to protect the host kernel, but
> has the potential to confuse guests without further virtualization.
> In particular, OVMF tries to size the VF BARs
The raw format layer supports all flags via passthrough - but
it only makes sense to pass through flags that the lower layer
actually supports.
Thanks to the previous patch, the raw format layer now attempts
to fragment writes at the max_transfer limit it inherits from
the NBD protocol layer,
Now that the block layer will honor max_transfer, we can simplify
our code to rely on that guarantee.
The readv code can call directly into nbd-client, just as the
writev code has done since commit 52a4650.
Interestingly enough, while qemu-io 'w 0 40m' splits into a 32M
and 8M transaction, 'w -z
Drivers should be able to rely on the block layer honoring the
max transfer length, rather than needing to return -EINVAL
(iscsi) or manually fragment things (nbd). This patch adds
the fragmentation in the block layer, after requests have been
aligned (fragmenting before alignment would lead to
Drivers should be able to rely on the block layer honoring the
max transfer length, rather than needing to return -EINVAL
(iscsi) or manually fragment things (nbd). We already fragment
write zeroes at the block layer; this patch adds the fragmentation
for normal writes, after requests have been
We have max_transfer documented in BlockLimits, but while we
honor it during pwrite_zeroes, we were blindly ignoring it
during pwritev and preadv, leading to multiple drivers having
to implement fragmentation themselves. This series moves
fragmentation to the block layer, then fixes the NBD
Now that NBD relies on the block layer to fragment things, we no
longer need to track an offset argument for which fragment of
a request we are actually servicing.
While at it, use true and false instead of 0 and 1 for a bool
parameter.
Signed-off-by: Eric Blake
---
On 20 June 2016 at 23:15, Joel Holdsworth
wrote:
> Even so, there is still the issue of the other glibc environment variables -
> see my LANG= example of the parent-guest wanting to run a child-guest
> Japanese, but the child-qemu should still run in English.
On 06/20/2016 09:19 AM, Denis V. Lunev wrote:
> From: Evgeny Yakovlev
>
> Some guests (win2008 server for example) do a lot of unnecessary
> flushing when underlying media has not changed. This adds additional
> overhead on host when calling fsync/fdatasync.
>
> This
On Mon, 20 Jun 2016 16:23:07 -0600
Eric Blake wrote:
> On 06/20/2016 04:04 PM, Alex Williamson wrote:
> > The kernel currently exposes the SR-IOV capability as read-only
> > through vfio-pci. This is sufficient to protect the host kernel, but
> > has the potential to confuse
On 06/20/2016 04:04 PM, Alex Williamson wrote:
> The kernel currently exposes the SR-IOV capability as read-only
> through vfio-pci. This is sufficient to protect the host kernel, but
> has the potential to confuse guests without further virtualization.
> In particular, OVMF tries to size the VF
On 20/06/16 22:40, Peter Maydell wrote:
On 20 June 2016 at 22:27, Joel Holdsworth
wrote:
The current behaviour was quite unexpected to me - there were no warnings,
and the need to link qemu statically isn't documented anywhere. If you
really believe that
The kernel currently exposes the SR-IOV capability as read-only
through vfio-pci. This is sufficient to protect the host kernel, but
has the potential to confuse guests without further virtualization.
In particular, OVMF tries to size the VF BARs and comes up with absurd
results, ending with an
On 20 June 2016 at 22:27, Joel Holdsworth
wrote:
> The current behaviour was quite unexpected to me - there were no warnings,
> and the need to link qemu statically isn't documented anywhere. If you
> really believe that static linking is the best answer here,
On 20/06/16 21:29, Laurent Vivier wrote:
Le 20/06/2016 à 21:51, Joel Holdsworth a écrit :
On 15/06/16 20:59, Laurent Vivier wrote:
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
Previously, when emulating execve(2), qemu would execute a child
instance of the emulator with the environment
On 18/06/16 07:03, Pranith Kumar wrote:
> diff --git a/tcg/tcg.h b/tcg/tcg.h
> index db6a062..36feca9 100644
> --- a/tcg/tcg.h
> +++ b/tcg/tcg.h
> @@ -408,6 +408,20 @@ static inline intptr_t QEMU_ARTIFICIAL
> GET_TCGV_PTR(TCGv_ptr t)
> #define TCG_CALL_DUMMY_TCGV MAKE_TCGV_I32(-1)
> #define
Hi Peter,
This update simply amends the MAINTAINERS entries for SPARC. Please pull.
ATB,
Mark.
The following changes since commit 7e13ea57f47710de2c19f22b27b34ab9fb045700:
Merge remote-tracking branch 'remotes/mwalle/tags/lm32-queue/20160620' into
staging (2016-06-20 18:14:26 +0100
From: "Daniel P. Berrange"
Move all trace-events for files in the qom/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-40-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the target-sparc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-37-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the linux-user/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Reviewed-by: Laurent Vivier
Message-id:
From: "Daniel P. Berrange"
Move all trace-events for files in the target-ppc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Reviewed-by: Thomas Huth
Message-id: 1466066426-16657-39-git-send-email-berra...@redhat.com
From: "Daniel P. Berrange"
Move all trace-events for files in the target-s390x/ directory to
their own file.
[Added missing newline in target-s390x/trace-events as suggested by
Cornelia Huck .
--Stefan]
Signed-off-by: Daniel P. Berrange
From: "Daniel P. Berrange"
Move all trace-events for files in the audio/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-35-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/pci/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-28-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the ui/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-34-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the net/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-36-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/isa/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-24-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/s390x/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Acked-by: Cornelia Huck
Message-id:
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/arm/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-32-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/sparc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-22-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/acpi/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-31-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/i386/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-25-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/vfio/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-30-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/ppc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Reviewed-by: Thomas Huth
Message-id: 1466066426-16657-27-git-send-email-berra...@redhat.com
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/dma/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-21-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/alpha/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-33-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/timer/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-20-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/input/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-19-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/sd/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-23-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/usb/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-15-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/9pfs/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-26-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/nvram/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-17-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/misc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-14-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/display/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-18-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/audio/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-13-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the block/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-7-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/char/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-9-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/net/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-11-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/scsi/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-16-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/intc/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-10-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/block/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-8-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the io/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-5-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the hw/virtio/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-12-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: Lluís Vilanova
The event is described in "trace-events". Note that the "MO_AMASK" flag
is not traced, since it does not seem to affect the visible semantics of
instructions.
[s/inline inline/inline/ to fix clang build.
--Stefan]
Signed-off-by: Lluís Vilanova
From: "Daniel P. Berrange"
Move all trace-events for files in the migration/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-6-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: "Daniel P. Berrange"
Move all trace-events for files in the util/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-3-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
The following changes since commit 5edbd4e30426d3a0d712510b2509a521e35192b1:
Merge remote-tracking branch 'remotes/otubo/tags/pull-seccomp-20160620' into
staging (2016-06-20 12:53:35 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/tracing-pull-request
From: "Daniel P. Berrange"
Move all trace-events for files in the crypto/ directory to
their own file.
Signed-off-by: Daniel P. Berrange
Message-id: 1466066426-16657-4-git-send-email-berra...@redhat.com
Signed-off-by: Stefan Hajnoczi
From: Lluís Vilanova
Information is tracked inside the TCGContext structure, and later used
by tracing events with the 'tcg' and 'vcpu' properties.
The 'cpu' field is used to check tracing of translation-time
events ("*_trans"). The 'tcg_env' field is used to pass it to
From: "Daniel P. Berrange"
Switch make rules over to use trace-events-all as the
master trace events input file. Add rule that will
construct trace-events-all from $(trace-events-y).
Signed-off-by: Daniel P. Berrange
Message-id:
Le 20/06/2016 à 21:51, Joel Holdsworth a écrit :
> On 15/06/16 20:59, Laurent Vivier wrote:
>>
>> Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
>>> Previously, when emulating execve(2), qemu would execute a child
>>> instance of the emulator with the environment variables provided by
>>> the
The command can be used to return host-specific CPU capabilities
information.
Signed-off-by: Eduardo Habkost
---
include/sysemu/arch_init.h | 1 +
qapi-schema.json | 36
qmp-commands.hx | 6 ++
The code that loads host-specific information inside
x86_cpu_realizefn() will be reused by the implementation of
query-host-cpu, so move it to a separate function.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 23 ---
1 file changed, 16
Add QMP command to allow management software to query for
CPU information for the running host.
The data returned by the command is in the form of a dictionary
of QOM properties.
This series depends on the "Add runnability info to
query-cpu-definitions" series I sent 2 weeks ago.
Git tree:
Return information on the host CPU using the "host" CPU model.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 64 +++
1 file changed, 64 insertions(+)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index
On 20 June 2016 at 20:16, Mark Cave-Ayland
wrote:
> Excellent! Another use case I see here is with HelenOS/ppc whose
> bootloader is fixed at address 0x800 (128Mb) and so if you don't
> increase the memory above the default then you end up with this panic,
>
Ping? No other feedback on this?
On Mon, Jun 06, 2016 at 05:05:37PM -0300, Eduardo Habkost wrote:
> This series extends query-cpu-definitions to include an extra
> field: "unavailable-features". The new field can be used to find
> out reasons that prevent the CPU model from running in the
>
20.6.2016 22.51 Joel Holdsworth
kirjoitti:
>
> On 15/06/16 20:59, Laurent Vivier wrote:
> >
> > Le 14/06/2016 `a 21:26, Joel Holdsworth a ecrit :
> >> Previously, when emulating execve(2), qemu would execute a child
> >> instance of the
On 15/06/16 20:31, Laurent Vivier wrote:
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
From: Petros Angelatos
In order for one to use QEMU user mode emulation under a chroot, it is
required to use binfmt_misc. This can be avoided by QEMU never doing a
raw execve() to
On 15/06/16 21:37, Laurent Vivier wrote:
This is not needed: if you use QEMU_STRACE environment variable, it is
propagated to the child processes (this is also true for "-L" and
QEMU_LD_PREFIX).
I would say that breaks the rule of least surprise for the user. If
we're going to invoke a child
On 15/06/16 21:06, Laurent Vivier wrote:
More details: why do we need this?
Add your Signed-off-by.
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
---
linux-user/syscall.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
On 15/06/16 20:59, Laurent Vivier wrote:
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
Previously, when emulating execve(2), qemu would execute a child
instance of the emulator with the environment variables provided by
the parent process. This caused problems with qemu if any of the
I started to port MPTimer tests to QTest that allows precise VM clock control.
It helped to find out that the last period of the periodic timer is getting
lost, i.e. when counter = 0 (before wrap around). So the counter should be
loaded with limit + 1 after wrapping around. This worked before
Attempting to cancel a dma_blk_io() request causes an abort(3):
void bdrv_aio_cancel(BlockAIOCB *acb)
{
...
while (acb->refcnt > 1) {
if (acb->aiocb_info->get_aio_context) {
aio_poll(acb->aiocb_info->get_aio_context(acb), true);
} else if
On 18/06/16 06:03, Richard Henderson wrote:
> There's a minor typo here that affects dumping of 64-bit
> registers on 32-bit hosts. Kind of embarrasing that this
> hasn't been seen previously.
>
> The main change takes care of cases wherein there's overlap
> between the indirect base register
1 - 100 of 409 matches
Mail list logo