On Mon, Apr 23, 2018 at 11:43:02AM +0530, Nikunj A Dadhania wrote:
> Set the newly added register(KVM_REG_PPC_ONLINE) to indicate if the vcpu is
> online(1) or offline(0)
>
> KVM will use this information to set the RWMR register, which controls the
> PURR
> and SPURR accumulation.
>
> CC: pau..
On Thu, Apr 19, 2018 at 02:42:58PM +0200, Cédric Le Goater wrote:
> The 'sent' status of the LSI interrupt source is modeled with the 'P'
> bit of the ESB and the assertion status of the source is maintained in
> an array under the main sPAPRXive object. The type of the source is
> stored in the sa
On Thu, Apr 19, 2018 at 02:42:59PM +0200, Cédric Le Goater wrote:
> The XiveFabric offers a simple interface, between the XiveSourve
> object and the device model owning the interrupt sources, to forward
> an event notification to the XIVE interrupt controller of the machine
> and if the owner is t
commit 1d3e65aa7ac5 ("hw/timer: Add value matching support to
aspeed_timer") increased the vmstate version of the timers array but
doing so, it broke migration. To fix, we also need to change the
vmstate version of the aspeed timer controller model.
Signed-off-by: Cédric Le Goater
---
To test o
Set the newly added register(KVM_REG_PPC_ONLINE) to indicate if the vcpu is
online(1) or offline(0)
KVM will use this information to set the RWMR register, which controls the PURR
and SPURR accumulation.
CC: pau...@samba.org
Signed-off-by: Nikunj A Dadhania
---
http://patchwork.ozlabs.org/patc
Introduce some hooks for the shared part of qemu thread between POSIX
and Windows implementations. Note that in qemu_mutex_unlock_impl() we
moved the call before unlock operation which should make more sense.
And we don't need qemu_mutex_post_unlock() hook.
Currently the hooks only calls the trac
We have had some tracing tools for mutex but it's not easy to use them
for e.g. dead locks. Let's provide "--enable-debug-mutex" parameter
when configure to allow QemuMutex to store the last owner that took
specific lock. It will be easy to use this tool to debug deadlocks
since we can directly k
From: "Emilio G. Cota"
This allows us to use atomic-add-bench as a microbenchmark
for evaluating qemu_mutex_lock's performance.
Signed-off-by: Emilio G. Cota
[cherry picked from https://github.com/cota/qemu/commit/f04f34df]
Signed-off-by: Peter Xu
---
tests/atomic_add-bench.c | 19 +++
Signed-off-by: Peter Xu
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index a80af735b2..87453edd88 100755
--- a/configure
+++ b/configure
@@ -1005,6 +1005,7 @@ for opt do
--enable-debug)
# Enable debugging options that aren't excessively noisy
v4:
- cherrypick Emilio's patch to add "-m" parameter to atomic_add-bench
tool.
- use inline functions [Emilio]
Micro benchmark result on "taskset -c 0 atomic_add-bench -m":
|+-+|
|| with --enable-debug | without --enable-debug |
|
On Fri, Apr 20, 2018 at 01:07:34PM -0400, Emilio G. Cota wrote:
> On Fri, Apr 20, 2018 at 12:42:10 +0800, Peter Xu wrote:
> > Put all the shared qemu-thread implementations into these files. The
> > header should be internal to qemu-thread but not for qemu-thread users.
> >
> > Introduce some hoo
From: Jan Kiszka
This allows to pin the host controller in the Linux PCI domain space.
Linux requires that property to be available consistently or not at all,
in which case the domain number becomes unstable on additions/removals.
Adding it here won't make a difference in practice for most setup
> >
> > Hello,
> >
> > This is good re-factoring and needed for 'virtio-pmem' as well to
> > reserve memory region in system address space.
> >
> > I have tested this code with virtio-pmem and its working fine. Thank you
> > for the work.
> >
> > I just have a small suggestion : when functions
I don't have the latest version yet, but I just tested it with 2.3.0 and
it works.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1254443
Title:
Periodic mode of LAPIC doesn't fire interrupts when u
On Fri, Apr 20, 2018 at 02:34:55PM +0200, David Hildenbrand wrote:
> Let's allow to query the MemoryHotplugState from the machine.
>
> This allows us to generically detect if a certain machine has support
> for memory devices, and to generically manage it (find free address
> range, plug/unplug a
On Fri, Apr 20, 2018 at 10:27:21AM +0200, Cédric Le Goater wrote:
> On 04/20/2018 09:10 AM, David Gibson wrote:
> > On Thu, Apr 19, 2018 at 02:42:57PM +0200, Cédric Le Goater wrote:
> >> Each XIVE interrupt source is associated with a two bit state machine
> >> called an Event State Buffer (ESB) :
On 21.04.2018 11:27, Mike R wrote:
> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to
> qemu-devel@nongnu.org
>
> reported.
Well, please also report:
- Which version of QEMU are you using?
- Which keyboard layout do you have on your physical keyboard?
- Which key did you pres
On 20.04.2018 21:56, Eduardo Habkost wrote:
> On Fri, Apr 20, 2018 at 03:19:28PM -0300, Eduardo Habkost wrote:
>> From: Amador Pahim
>>
>> This patch adds the QEMUMachine._create_console() method, which
>> returns a list with the chardev console device arguments to be
>> used in the qemu command l
On 20.04.2018 19:33, Jason Wagner wrote:
> I'm seeing this issue in version 2.12.0-rc4. I wasn't seeing this as
> much in earlier 2.11, but its a major pain in the current version.
Any chance you could bi-sect this issue to find out which commit exactly
is causing the problem?
Thomas
On Sun, Apr 22, 2018 at 11:41:20AM +0100, Peter Maydell wrote:
> On 21 April 2018 at 22:16, Philippe Mathieu-Daudé wrote:
> > This fixes the following ASan warning:
> >
> > $ mips64el-softmmu/qemu-system-mips64el -M boston -kernel vmlinux.gz.itb
> > -nographic
> > hw/core/loader-fit.c:108:17:
On 2018-04-09 10:08 PM, Stefan Hajnoczi wrote:
> I wonder what the point of select-frame is then...
>
> I have CCed the GDB mailing list. Maybe someone can help us. Context:
>
> QEMU implements coroutines using jmpbuf. We'd like to print coroutine
> call stacks in GDB and have a script that wo
On Fri, Apr 20, 2018 at 10:34:57AM +0100, Daniel P. Berrangé wrote:
> On Fri, Apr 20, 2018 at 10:11:08AM +0200, Laszlo Ersek wrote:
> > On 04/19/18 11:12, Daniel P. Berrangé wrote:
> > > On Thu, Apr 19, 2018 at 10:39:32AM +0200, Laszlo Ersek wrote:
> > >> On 04/19/18 09:56, Daniel P. Berrangé wrote
> On Fri, Feb 2, 2018 at 1:49 PM, Alistair Francis
> wrote:
>> On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>>>
>>> Alistair Francis writes:
>>>
On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
wrote:
> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée
> wrote:
>>
>
On 04/19/2018 03:58 AM, Alex Bennée wrote:
> What would be really
> helpful is if the respective maintainers could encode their EXACT
> STEPS for building their cross compilers into some docker recipes.
I've just re-built my alphaev67 cross-environment and recorded everything.
Since the script be
On 04/20/2018 08:55 AM, Emilio G. Cota wrote:
> - Added an assert in translate_insn, before exiting due to an exception,
> to make sure that is_jmp is set to DISAS_EXCP (the exception generation
> function always sets it.)
Comment is out of date -- s/EXCP/NORETURN/.
r~
On 04/20/2018 08:55 AM, Emilio G. Cota wrote:
> +#define DISAS_STOP DISAS_TARGET_0
> +#define DISAS_EXCP DISAS_TARGET_1
> +#define DISAS_EXIT DISAS_TARGET_2
DISAS_EXCP should be unused and therefore not exist.
> @@ -8301,7 +8298,7 @@ static void gen_cp0 (CPUMIPSState *env, Disas
On 04/20/2018 08:55 AM, Emilio G. Cota wrote:
> The TB after BS_STOP is not fixed (e.g. helper_mtc0_hwrena
> changes hflags, which ends up changing the TB flags via
> cpu_get_tb_cpu_state). This requires a full lookup (i.e.
> with flags) via lookup_and_goto_ptr instead of gen_goto_tb,
> since the l
On 04/21/2018 01:21 PM, Philippe Mathieu-Daudé wrote:
> This fixes the following ASan warning:
>
> $ qemu-system-xtensa -M kc705 -m 128M -semihosting -nographic -monitor null
> -kernel Image.elf
> include/hw/elf_ops.h:179:5: runtime error: null pointer passed as argument
> 1, which is declar
On 04/19/2018 07:51 AM, Cornelia Huck wrote:
On Sun, 15 Apr 2018 15:07:19 -0400
Tony Krowiak wrote:
default-configs/s390x-softmmu.mak |1 +
docs/vfio-ap.txt | 649 +
hw/s390x/Makefile.objs|1 +
hw/s390x/ap-device.c
On 04/22/2018 12:01 PM, Halil Pasic wrote:
On 04/22/2018 05:43 PM, Tony Krowiak wrote:
+FEAT_INIT_MISC("ap", "AP facilities installed"),
Why plural ('facilities')? Would not s/facilities/instructions be
more end-user
friendly?
It's a matter of opinion. I prefer facilities because AP
On 04/19/2018 08:03 AM, Cornelia Huck wrote:
On Sun, 15 Apr 2018 15:07:23 -0400
Tony Krowiak wrote:
Introduces a VFIO based AP device. The device is defined via
the QEMU command line by specifying:
-device vfio-ap,sysfsdev=
There may be only one vfio-ap device configured for a guest.
T
On 04/22/2018 05:43 PM, Tony Krowiak wrote:
+FEAT_INIT_MISC("ap", "AP facilities installed"),
Why plural ('facilities')? Would not s/facilities/instructions be more end-user
friendly?
It's a matter of opinion. I prefer facilities because AP is comprised of not
only
instructions, but al
On 04/22/2018 05:52 PM, Tony Krowiak wrote:
+ FEAT_INIT("apqci", S390_FEAT_TYPE_STFL, 12, "Query AP Configuration
facility"),
Why did you change this form qci to apqci. Too may people found the
qci good?
I changed it by request and I thought it made sense to do so. Maybe we should
just
On 04/18/2018 05:11 AM, Pierre Morel wrote:
On 15/04/2018 21:07, Tony Krowiak wrote:
Introduces a VFIO based AP device. The device is defined via
the QEMU command line by specifying:
-device vfio-ap,sysfsdev=
There may be only one vfio-ap device configured for a guest.
The mediated matri
On 04/18/2018 07:03 AM, David Hildenbrand wrote:
On 18.04.2018 12:55, Halil Pasic wrote:
On 04/15/2018 09:07 PM, Tony Krowiak wrote:
A new CPU model feature and two new CPU model facilities are
introduced to support AP devices for a KVM guest.
[..]
diff --git a/target/s390x/cpu_features.c b/
On 04/18/2018 06:55 AM, Halil Pasic wrote:
On 04/15/2018 09:07 PM, Tony Krowiak wrote:
A new CPU model feature and two new CPU model facilities are
introduced to support AP devices for a KVM guest.
[..]
diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
index 3b9e274..5ee
On 04/18/2018 06:55 AM, Halil Pasic wrote:
On 04/15/2018 09:07 PM, Tony Krowiak wrote:
A new CPU model feature and two new CPU model facilities are
introduced to support AP devices for a KVM guest.
[..]
diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
index 3b9e274..5ee
On 04/18/2018 04:59 AM, David Hildenbrand wrote:
On 18.04.2018 09:40, Cornelia Huck wrote:
On Tue, 17 Apr 2018 20:21:31 +0200
Christian Borntraeger wrote:
On 04/16/2018 05:44 PM, David Hildenbrand wrote:
diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
index 0cdb
On 04/18/2018 03:40 AM, Cornelia Huck wrote:
On Tue, 17 Apr 2018 20:21:31 +0200
Christian Borntraeger wrote:
On 04/16/2018 05:44 PM, David Hildenbrand wrote:
diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
index 0cdbc15..0d5b0f7 100644
--- a/target/s390x/gen-feat
On 04/18/2018 05:16 AM, Pierre Morel wrote:
On 15/04/2018 21:07, Tony Krowiak wrote:
This patch introduces the base object for an AP device.
Signed-off-by: Tony Krowiak
---
hw/s390x/Makefile.objs |1 +
hw/s390x/ap-device.c | 39
+++
On Sun, Apr 22, 2018 at 10:21:34AM +0200, David Hildenbrand wrote:
> On 22.04.2018 06:26, David Gibson wrote:
> > On Fri, Apr 20, 2018 at 02:34:54PM +0200, David Hildenbrand wrote:
> >> On the qmp level, we already have the concept of memory devices:
> >> "query-memory-devices"
> >> Right now,
On 21 April 2018 at 22:16, Philippe Mathieu-Daudé wrote:
> This fixes the following ASan warning:
>
> $ mips64el-softmmu/qemu-system-mips64el -M boston -kernel vmlinux.gz.itb
> -nographic
> hw/core/loader-fit.c:108:17: runtime error: load of misaligned address
> 0x7f95cd7e4264 for type 'fdt6
On Tue, Apr 17, 2018 at 04:18:43PM -0500, Eric Blake wrote:
> Focusing on just the interface:
>
>> +++ b/qapi/misc.json
>> @@ -1185,6 +1185,26 @@
>> { 'command': 'pmemsave',
>>'data': {'val': 'int', 'size': 'int', 'filename': 'str'} }
>>
>> +##
>> +# @pmemload:
>> +#
>> +# Load a portion of gu
On Tue, Apr 17, 2018 at 03:56:58PM -0500, Eric Blake wrote:
> On 04/12/2018 07:50 AM, Simon Ruderich wrote:
>> Signed-off-by: Simon Ruderich
>> ---
>> cpus.c | 6 --
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> Reviewed-by: Eric Blake
>
> However, as a meta-comment, this message wa
>> +typedef struct MemoryDeviceClass {
>> +InterfaceClass parent_class;
>> +
>> +uint64_t (*get_addr)(MemoryDeviceState *md);
>> +uint64_t (*get_plugged_size)(MemoryDeviceState *md, Error **errp);
>> +uint64_t (*get_region_size)(MemoryDeviceState *md, Error **errp);
>
> Just not su
On 22.04.2018 06:26, David Gibson wrote:
> On Fri, Apr 20, 2018 at 02:34:54PM +0200, David Hildenbrand wrote:
>> On the qmp level, we already have the concept of memory devices:
>> "query-memory-devices"
>> Right now, we only support NVDIMM and PCDIMM.
>>
>> We want to map other devices later i
On 22.04.2018 06:58, Pankaj Gupta wrote:
>
> Hello,
>
> This is good re-factoring and needed for 'virtio-pmem' as well to
> reserve memory region in system address space.
>
> I have tested this code with virtio-pmem and its working fine. Thank you
> for the work.
>
> I just have a small suggest
47 matches
Mail list logo
