Enable CONFIG_QEMU_LDST_OPTIMIZATION for TCG qemu_ld/st optimization only when
a host is i386 or x86_64.
Signed-off-by: Yeongkyoon Lee yeongkyoon@samsung.com
---
configure |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index
Add GETPC_EXT which is used by MMU helpers to selectively calculate the code
address of accessing guest memory when called from a qemu_ld/st optimized code
or a C function. Currently, it supports only i386 and x86-64 hosts.
Signed-off-by: Yeongkyoon Lee yeongkyoon@samsung.com
---
exec-all.h
Add optimized TCG qemu_ld/st generation which locates the code of TLB miss
cases at the end of a block after generating the other IRs.
Currently, this optimization supports only i386 and x86_64 hosts.
Signed-off-by: Yeongkyoon Lee yeongkyoon@samsung.com
---
tcg/i386/tcg-target.c | 415
Let me resend this patch, because it looks ignored except for the comment from
Richard Henderson for which I've replied.
Here is the 6th version of the series optimizing TCG qemu_ld/st code generation.
v6:
- Remove an extra argument of return addr from MMU helpers
Instead, embed the fast
On Mon, Oct 15, 2012 at 6:02 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
This patch series adds a mmio bar to the standard vga. It also drops
a file into docs/specs/ describing the mmio bar and the other properties
of the qemu standard vga and does a little cleanup by removing
Thanks, applied all.
On Tue, Oct 16, 2012 at 7:30 AM, Richard Henderson r...@twiddle.net wrote:
Changes v3-v4:
* Patch 5 actually included,
* Patch 1 updates printf format for changed size_t.
r~
Richard Henderson (5):
exec: Split up and tidy code_gen_buffer
exec: Don't make
On Tue, Oct 16, 2012 at 9:32 AM, Richard Henderson r...@twiddle.net wrote:
The primary goal of this patch set is to have all references to windowed
registers to go through new routines that have access to DisasContext.
This is a prerequisite to any change in how windowed registers might be
On Thu, Oct 18, 2012 at 1:11 PM, Peter Maydell peter.mayd...@linaro.org wrote:
This patch series introduces a new logging category to
qemu_log_mask(), for reporting situations which the device
model can cope with but which indicate bugs in the guest.
The most common cause of these is guest
On Tue, Oct 16, 2012 at 11:28 PM, Aurelien Jarno aurel...@aurel32.net wrote:
Like the MOVr instruction, the FMOVr instruction has the condition
encoded between bits 10 and 12.
Thanks, applied.
Cc: Blue Swirl blauwir...@gmail.com
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
Il 19/10/2012 18:19, Kevin Wolf ha scritto:
Am 18.10.2012 16:49, schrieb Paolo Bonzini:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
v2-v3: new testcases test_cancel_after_ready and
test_medium_not_found, removed obsolete workaround
for os.remove failure.
qemu-user needs SIGSEGV (at least) for some internal use. If the guest
application masks it and does unsafe sigprocmask, then the application
crashes. Problems happen in applications with self-modifying code (who
also change the signal mask). Other guest applications may have related
problems if
Create a wrapper for signal mask changes initiated by the guest;
(this includes syscalls and also the sigreturns from signal.c)
this will give us a place to put code which prevents the guest
from changing the handling of signals used by QEMU itself
internally.
The wrapper is called from all the
Create a safe wrapper by protecting the signal mask.
Instead of doing a simple passthrough of the sigprocmask, the wrapper
manipulates the signal mask in a safe way for the qemu internal. This
is done by avoiding SIGSEGV bit mask manipulation from the guest.
We also return the same bit on the
Commit 5793f2a47e201d251856c7956d6f7907ec0d9f1f causes data corruption
in system mode:
| [] Synthesizing the initial hotplug events...udevd[291]: timeout: killing
'net.agent' [302]
| udevd[291]: 'net.agent' [302] terminated by signal 9 (Killed)
| udevd[299]: timeout: killing '/sbin/modprobe
On 20.10.2012 00:43, Jason Baron wrote:
Hi,
Qemu bits for q35 support, I'm posting the seabios changes separately. The
patches require '-M pc_q35' and -L 'seabios dir with q35 changes' on the
Just a small maybe-nitpick: can we ue pc-q35 here instead of pc_q35 (ie,
minus instead of
Now that CONFIG_TCG_PASS_AREG0 has been removed, it's easier to get
an optimal code for the load/store functions.
First swap the two registers used in tcg_out_tlb_load() so that the
address end-up in the second register instead of the first one. Adjust
tcg_out_qemu_ld() and tcg_out_qemu_st() to
On x86_64, remove the constraint on the third argument register which
is not needed:
- For loads the helper arguments are env, addr, mem_idx. The addr
value should not be in the two first argument registers as they are
used in tcg_out_tlb_load().
- For stores the helper arguments are env,
Public bug reported:
Thread cancellation (and certain other implementation-internal things
such as set*id() and timers) are implemented in userspace on Linux by
stealing a couple of the realtime signals for internal use by the
implementation, leaving them unavailable to applications.
Patch for the issue is available here:
https://lists.eait.uq.edu.au/pipermail/microblaze-
linux/2012-October/005760.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread
Rather than printing a message saying we're silently falling
back to gthread coroutines when running on MacOS, actually
do it silently.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
I guess this is a self-falsifying echo :-)
configure | 2 --
1 file changed, 2 deletions(-)
diff
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread cancellation broken in app-level emulation
Status in QEMU:
Fix
Arg, somehow I added the above comment on the wrong bug. Thus bug is not
fixed. The other bug report I recently filed was fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread
I accidentally posted the patch, which is here, on the wrong bug report
(1068900 instead of here). Apologies. For reference here is the patch;
it was committed and fixes this issue:
https://lists.eait.uq.edu.au/pipermail/microblaze-
linux/2012-October/005760.html
Issue # 1068900, where I
The current implementation of pci_find_space does not correctly align
PCI capabilities in the PCI configuration space. It also does not
support PCI-Express devices. This patch fixes these issues.
Thanks to Alex Williamson for feedback.
Signed-off-by: Matt Renzelmann m...@cs.wisc.edu
---
On 2012-10-21 00:48, Aurelien Jarno wrote:
I am not sure it is the real problem, but at least the optimization of
using the destination register as a temporary is wrong when the
instruction might trigger an exception. In that case the result is
written to the destination register while it
On Sun, Oct 21, 2012 at 08:48:52AM +1000, Richard Henderson wrote:
On 2012-10-21 00:48, Aurelien Jarno wrote:
I am not sure it is the real problem, but at least the optimization of
using the destination register as a temporary is wrong when the
instruction might trigger an exception. In
** Changed in: qemu
Status: Fix Committed = New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread cancellation broken in app-level emulation
Status in QEMU:
New
Bug
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1066909
Title:
App-level clone emulation for microblaze is broken
Status in QEMU:
Fix
On Mon, Oct 15, 2012 at 03:57:54PM -0300, Luiz Capitulino wrote:
On Fri, 5 Oct 2012 16:47:57 -0300
Luiz Capitulino lcapitul...@redhat.com wrote:
This makes it possible for QEMU to use transparent huge pages (THP)
when transparent_hugepage/enabled=madvise. Otherwise THP is only
used when
On Thu, Oct 18, 2012 at 01:36:05PM +1000, Richard Henderson wrote:
When we allocate a reserved_va for the guest, the kernel will likely
choose an address well above 4G. At which point we must use a pair
of movabsq+addq to form the host address. If we have OS support,
set up a segment
30 matches
Mail list logo