On Thu, Aug 06, 2015 at 10:57:13AM +0530, Bharata B Rao wrote:
> Start supporting CPU hotplug from pseries-2.5 onwards. Add CPU
> DRC (Dynamic Resource Connector) device tree entries.
>
> Signed-off-by: Bharata B Rao
Reviewed-by: David Gibson
--
David Gibson| I'll have my
On Thu, Aug 06, 2015 at 10:57:14AM +0530, Bharata B Rao wrote:
> Support CPU hotplug via device-add command. Set up device tree
> entries for the hotplugged CPU core and use the exising EPOW event
> infrastructure to send CPU hotplug notification to the guest.
>
> Create only cores explicitly from
"Daniel P. Berrange" writes:
> On Thu, Sep 03, 2015 at 04:29:53PM +0200, Markus Armbruster wrote:
>> The QAPI code generators work with a syntax tree (nested dictionaries)
>> plus a few symbol tables (also dictionaries) on the side.
>>
>> They have clearly outgrown these simple data structures.
Hi Stefan,
On Wed, 2 Sep 2015 14:48:57 +0100 Stefan Hajnoczi wrote:
> On Thu, Aug 20, 2015 at 02:45:47AM +0800, Fam Zheng wrote:
> > Looks like the previous patch to fix this fell between the cracks and never
> > made it to qemu.git?
> >
> > http://patchwork.ozlabs.org/patch/489847/
> >
> > Ste
Hi!
> Something in your patch submission path seems to be wrapping long
> lines. It would be nice if you could fix it -- I couldn't apply this
> patch without manually editing it first.
Damn, stupid Outlook... I already set maximum width to ~100, ok, will increase
it further.
> We should add
Eric Blake writes:
> On 09/03/2015 08:30 AM, Markus Armbruster wrote:
>> 'gen': false needs to stay for now, because netdev_add is still using
>> it.
>>
>> Signed-off-by: Markus Armbruster
>> Reviewed-by: Eric Blake
>> ---
>
>> +++ b/tests/Makefile
>> @@ -228,7 +228,7 @@ check-qapi-schema-y :=
Michael Roth writes:
> Quoting Eric Blake (2015-09-03 15:50:16)
>> On 09/03/2015 08:30 AM, Markus Armbruster wrote:
>> > qapi/introspect.json defines the introspection schema. It's designed
>> > for QMP introspection, but should do for similar uses, such as QGA.
>>
>> [review to follow in separ
On Thu, Aug 06, 2015 at 10:57:15AM +0530, Bharata B Rao wrote:
> QEMU currently supports CPU topologies where there can be cores
> which are not completely filled with all the threads as per the
> specifed SMT mode.
>
> Restore support for such topologies (Eg -smp 15,cores=4,threads=4)
> The last
On Wed, Aug 19, 2015 at 12:26:11PM +0530, Bharata B Rao wrote:
> Add support to hot remove pc-dimm memory devices.
>
> Signed-off-by: Bharata B Rao
> ---
> hw/ppc/spapr.c | 114
> -
> hw/ppc/spapr_drc.c | 21 +
> include/hw/pp
On Wed, Aug 19, 2015 at 12:26:10PM +0530, Bharata B Rao wrote:
> drck->set_isolation_state() can return error. For such a case ensure
> correct error is returned by rtas_set_indicator() instead of always
> returning success.
>
> TODO: rtas_st(, , uint32 val) => the return value uint32, but
> drck-
Hello!
> Why have separate ITS_CONTROL and ITS_TRANSLATION entries, given
> that the ITS pages are architecturally required to be contiguous
> and the dt binding doesn't require you to specify the two addresses
> separately?
It is more convenient for ITS implementation. I already have the code
03.09.2015 19:35, Peter Maydell пишет:
On 3 September 2015 at 15:31, Sergey Smolov wrote:
Do you think it is possible to implement another QEMU logger which will
make a record for every executed block,
Yes (this would just need to disable the TB linking optimisation,
which we've discussed pr
For a easy creation of device directly form sdhci, without building a wrapper
around.
Signed-off-by: Sai Pavan Boddu
---
hw/sd/sdhci.c | 2 +-
{hw/sd => include/hw}/sdhci.h | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename {hw/sd => include/hw}/sdhci.h (100%)
diff --g
Hi,
At KVM Forum I sat down with Paolo and Frederic and we came up with the
current outstanding tasks on MTTCG. This is not comprehensive but
hopefully covers the big areas. They are sorted in rough order we'd like
to get them up-streamed.
* linux-user patches (Paolo)
Paolo has already grabbed a
Hi Alex,
On 04/09/2015 09:49, Alex Bennée wrote:
Hi,
At KVM Forum I sat down with Paolo and Frederic and we came up with the
current outstanding tasks on MTTCG. This is not comprehensive but
hopefully covers the big areas. They are sorted in rough order we'd like
to get them up-streamed.
* lin
On 03/09/2015 22:48, Aníbal Limón wrote:
> When QEMU starts the RCU thread executes qemu_mutex_lock_thread
> causing error "qemu:qemu_cpu_kick_thread: No such process" and exits.
>
> This isn't occur frequently but in glibc the thread id can exist and
> this not guarantee that the thread is on a
On 04/09/15 09:01, David Gibson wrote:
> On Thu, Aug 06, 2015 at 10:57:15AM +0530, Bharata B Rao wrote:
>> QEMU currently supports CPU topologies where there can be cores
>> which are not completely filled with all the threads as per the
>> specifed SMT mode.
>>
>> Restore support for such topologi
On 4 September 2015 at 07:54, Pavel Fedin wrote:
> Hello!
>
>> > +
>> > +#define kvm_gicd_access(s, offset, cpu, val, write) \
>> > +kvm_device_access(s->dev_fd, KVM_DEV_ARM_VGIC_GRP_DIST_REGS, \
>> > + KVM_VGIC_ATTR(offset, cpu), val, write)
>> > +
>> > +#define kvm_gicc
On 24/08/2015 02:23, Emilio G. Cota wrote:
> This paves the way for a lockless tb_find_fast.
Having now reviewed the patch, I think we can do better.
The idea is:
- only the CPU thread can set cpu->tb_jmp_cache[]
- other threads can, under seqlock protection, _clear_ cpu->tb_jmp_cache[]
- th
On 4 September 2015 at 08:13, Pavel Fedin wrote:
>> We should add a note to QEMU's changelog to mention that if
>> they have a 32-bit kernel on the virt board and the PCI has
>> stopped working then they need to use this option.
>> (http://wiki.qemu.org/ChangeLog/2.5)
>
> I tried to, but "log in"
On Fri, Sep 04, 2015 at 09:12:09AM +0200, Markus Armbruster wrote:
> "Daniel P. Berrange" writes:
>
> > On Thu, Sep 03, 2015 at 04:29:53PM +0200, Markus Armbruster wrote:
> > Python has a nice tool called pep8 which can apply a
> > configurable bunch of style checks, it is probably
> > worth som
Am 20.08.2015 um 23:54 schrieb Eduardo Habkost:
> Machine class names should use the "-machine" suffix to allow
> class-name-based machine class lookup to work. Rename the
> s390-ccw-virtio-2.4 machine class using the MACHINE_TYPE_NAME macro.
>
> Cc: Alexander Graf
> Cc: Cornelia Huck
> Cc: Chri
Hi!
> Yeah, we only let people with accounts create new ones, to
> avoid spam. If you tell me what username you'd like I'll
> create an account for you.
p.fedin or pfedin, depending on whether dots are allowed or not.
> Can you test this reasonably soon, please? Otherwise
> I'll have to drop i
On Wed, Sep 2, 2015 at 9:36 PM, Vasiliy Tolstov wrote:
> 2015-09-01 6:03 GMT+03:00 Hitoshi Mitake :
>> This patch refines discard support of the sheepdog driver. The
>> existing discard mechanism was implemented on SD_OP_DISCARD_OBJ, which
>> was introduced before fine grained reference counting o
On 4 September 2015 at 08:26, Pavel Fedin wrote:
> Hello!
>
>> Why have separate ITS_CONTROL and ITS_TRANSLATION entries, given
>> that the ITS pages are architecturally required to be contiguous
>> and the dt binding doesn't require you to specify the two addresses
>> separately?
>
> It is more
We allow guests to change the size of the virtqueue rings by supplying
a number of buffers that is different from the number of buffers the
device was initialized with. Current code has some problems, however,
since reset does not reset the ringsizes to the default values (as this
is not saved anyw
Hi,
here's a set of patches for virtio-core and virtio-ccw, fixing a common
code issue and finally enabling virtio-1 for ccw devices.
The first issue was noted by Jason: We need to care about changed
ring sizes. We also want to support different ring sizes in ccw for
virtio-1 devices (existing co
Let's enable revision 1 for virtio-ccw devices. We can always offer
VERSION_1 as drivers in legacy mode won't be able to see it anyway.
We have to introduce a way to set a lower maximum revision for a device
to accommodate the following cases:
- compat machines (to enforce legacy only)
- virtio-bl
Wire up changing the ring size for virtio-1 devices.
Signed-off-by: Cornelia Huck
---
hw/s390x/virtio-ccw.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
index d36373e..85e2a5d 100644
--- a/hw/s390x/virtio-ccw.c
+
Michael Roth writes:
> Quoting Markus Armbruster (2015-09-03 09:30:21)
>> qapi/introspect.json defines the introspection schema. It's designed
>> for QMP introspection, but should do for similar uses, such as QGA.
>>
>> The introspection schema does not reflect all the rules and
>> restrictions
We currently switch off the VERSION_1 feature bit if the guest has
not negotiated at least revision 1. As no feature bits beyond 31 are
valid however unless VERSION_1 has been negotiated, make sure that
legacy guests never see a feature bit beyond 31.
Signed-off-by: Cornelia Huck
---
hw/s390x/vi
On 04/09/2015 01:34, Alistair Francis wrote:
On Thu, Sep 3, 2015 at 12:28 AM, Frederic Konrad
wrote:
On 02/09/2015 23:39, Alistair Francis wrote:
On Tue, Jul 21, 2015 at 10:17 AM, wrote:
From: KONRAD Frederic
This is the implementation of the DPDMA.
Signed-off-by: KONRAD Frederic
---
On 04/09/2015 09:49, Alex Bennée wrote:
> * Signal free qemu_cpu_kick (Paolo)
>
> I don't know much about this patch set but I assume this avoids the need
> to catch signals and longjmp about just to wake up?
It was part of Fred's patches, so I've extracted it to its own series.
Removing 150 li
Hello!
> Can you test this reasonably soon, please? Otherwise
> I'll have to drop it from target-arm again.
Tested, confirm, the problem persists with Linux v4.1.4, LPAE disabled:
--- cut ---
PCI host bridge /pcie@1000 ranges:
IO 0x3eff..0x3eff -> 0x
MEM 0x1000..0x3
On Fri, Sep 04, 2015 at 11:25:33AM +0200, Paolo Bonzini wrote:
>
>
> On 04/09/2015 09:49, Alex Bennée wrote:
> > * Signal free qemu_cpu_kick (Paolo)
> >
> > I don't know much about this patch set but I assume this avoids the need
> > to catch signals and longjmp about just to wake up?
>
> It wa
On 9/3/15 22:53, Eric Blake wrote:
> On 09/02/2015 07:30 PM, Richard Henderson wrote:
>> From: Chen Gang
>
> s/Firstly add/Add/ in the subject line
>
Thank you for your careful notification. :-)
I guess, it will be modified by RTH, before the patches v15 (or v16) are
integrated into qemu master
Eric Blake writes:
> On 09/03/2015 08:30 AM, Markus Armbruster wrote:
>> qapi/introspect.json defines the introspection schema. It's designed
>> for QMP introspection, but should do for similar uses, such as QGA.
>
> [review in this sub-thread; for comments on 'int' munging or other
> followups,
On Fri, Sep 4, 2015 at 5:51 PM, Hitoshi Mitake wrote:
> On Wed, Sep 2, 2015 at 9:36 PM, Vasiliy Tolstov wrote:
>> 2015-09-01 6:03 GMT+03:00 Hitoshi Mitake :
>>> This patch refines discard support of the sheepdog driver. The
>>> existing discard mechanism was implemented on SD_OP_DISCARD_OBJ, whic
On 04/09/2015 10:50, Paolo Bonzini wrote:
> Having now reviewed the patch, I think we can do better.
>
> The idea is:
>
> - only the CPU thread can set cpu->tb_jmp_cache[]
>
> - other threads can, under seqlock protection, _clear_ cpu->tb_jmp_cache[]
>
> - the seqlock can be protected by tb_l
> On 4 Sep 2015, at 11:41, Edgar E. Iglesias wrote:
>
> On Fri, Sep 04, 2015 at 11:25:33AM +0200, Paolo Bonzini wrote:
>>
>>
>> On 04/09/2015 09:49, Alex Bennée wrote:
>>> * Signal free qemu_cpu_kick (Paolo)
>>>
>>> I don't know much about this patch set but I assume this avoids the need
>>>
We're seeing repeated segfaults in qemu-system-arm when we heavily use
the network. I have a coredump backtrace:
Reading symbols from
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm...done.
[New LWP 4536]
[New LWP 4534]
04 сент. 2015 г. 12:57 пользователь "Hitoshi Mitake" <
mitake.hito...@gmail.com> написал:
>
> On Fri, Sep 4, 2015 at 5:51 PM, Hitoshi Mitake
wrote:
> > On Wed, Sep 2, 2015 at 9:36 PM, Vasiliy Tolstov
wrote:
> >> 2015-09-01 6:03 GMT+03:00 Hitoshi Mitake :
> >>> This patch refines discard support o
On Thu, Sep 03, 2015 at 12:18:18AM +0800, Yang Hongyang wrote:
>
>
> On 09/02/2015 09:02 PM, Stefan Hajnoczi wrote:
> >On Wed, Sep 02, 2015 at 09:49:18AM +0800, Yang Hongyang wrote:
> >>On 09/01/2015 10:43 PM, Stefan Hajnoczi wrote:
> >>>On Tue, Sep 01, 2015 at 05:06:18PM +0800, Yang Hongyang wro
On 4 September 2015 at 11:25, Richard Purdie
wrote:
> We're seeing repeated segfaults in qemu-system-arm when we heavily use
> the network. I have a coredump backtrace:
> (gdb) print s->tx_fifo_done
> $1 = {99614720, 99614720, 99614720, 99614720}
> (gdb) print s->tx_fifo_done_len
> $2 = 99614719
On Wed, Sep 02, 2015 at 11:25:26AM +0200, Alexander Spyridakis wrote:
> Properly clean any generated object and binary files after a 'make clean',
> this fixes an issue when trying to reconfigure between arm and arm64.
Are you also running configure (with the opposite arch selected) after
'make cl
On 02/09/2015 23:50, Richard Henderson wrote:
> We can tidy gen_load_fpr32h, as well as introduce a helper
> to cleanup the MACC instructions.
>
> Signed-off-by: Richard Henderson
> ---
> target-mips/translate.c | 48 ++--
> 1 file changed, 22 insertio
"Daniel P. Berrange" writes:
> On Fri, Sep 04, 2015 at 09:12:09AM +0200, Markus Armbruster wrote:
>> "Daniel P. Berrange" writes:
>>
>> > On Thu, Sep 03, 2015 at 04:29:53PM +0200, Markus Armbruster wrote:
>> > Python has a nice tool called pep8 which can apply a
>> > configurable bunch of styl
On Fri, 2015-09-04 at 11:45 +0100, Peter Maydell wrote:
> On 4 September 2015 at 11:25, Richard Purdie
> wrote:
> > We're seeing repeated segfaults in qemu-system-arm when we heavily use
> > the network. I have a coredump backtrace:
>
> > (gdb) print s->tx_fifo_done
> > $1 = {99614720, 99614720,
On 4 September 2015 at 12:24, Richard Purdie
wrote:
> So just based on that, yes, seems that the rx_fifo looks to be
> overrunning. I can add the asserts but I think it would just confirm
> this.
Yes, the point of adding assertions is to confirm a hypothesis.
>> Also, do you have a more specific
Introduces reusable definitions for CPU affinity masks/shifts and gets rid
of hardcoded magic numbers.
Signed-off-by: Pavel Fedin
---
target-arm/cpu-qom.h | 12
target-arm/cpu.c | 2 +-
target-arm/kvm32.c | 3 +--
target-arm/kvm64.c | 3 +--
4 files changed, 15 insertions
This small patchset is actually a small extraction from vGICv3 support,
as it was suggested in
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00921.html.
Initially i wanted to just make a check, but ended up full implementation
which is not more difficult. Since we don't make any assumpti
At least with KVM, currently there's no reason why qemu would not be
capable of handling Aff3 != 0. This commit fixes up FDT creation in such
a case.
Signed-off-by: Pavel Fedin
---
hw/arm/virt.c | 32 ++--
1 file changed, 30 insertions(+), 2 deletions(-)
diff --git a
On Fri, 14 Aug 2015 22:52:00 +0800
Xiao Guangrong wrote:
> NVDIMM reserves all the free range above 4G to do:
> - Persistent Memory (PMEM) mapping
> - implement NVDIMM ACPI device _DSM method
>
> Signed-off-by: Xiao Guangrong
> ---
> hw/i386/pc.c | 12 ++--
> hw/mem/nvdim
This is a brief writeup of what we discussed at the QEMU Summit 2015
at KVM Forum last month.
* Participants
Markus Armbruster
Paolo Bonzini
Luiz Capitulino
Andreas Färber
Alexander Graf
Eduardo Habkost
Stefan Hajnoczi
Richard Henderson
Gerd Hoffmann
Edgar E. Iglesias
Bastian Koppelmann
Peter May
On 09/03/2015 08:29 AM, Markus Armbruster wrote:
> The QAPI code generators work with a syntax tree (nested dictionaries)
> plus a few symbol tables (also dictionaries) on the side.
>
> +
> +class QAPISchemaArrayType(QAPISchemaType):
> +def __init__(self, name, info, element_type):
> +
We will introduce the 'blockdev-snapshot' command that will require
its own struct for the parameters, so we need to rename this one in
order to avoid name clashes.
Signed-off-by: Alberto Garcia
---
blockdev.c | 2 +-
qapi-schema.json | 2 +-
qapi/block-core.json | 8
3 fi
One of the limitations of the 'blockdev-snapshot-sync' command is that
it does not allow passing BlockdevOptions to the newly created
snapshots, so they are always opened using the default values.
Extending the command to allow passing options is not a practical
solution because there is overlap b
Previous attempt to extend blockdev-snapshot-sync:
https://lists.gnu.org/archive/html/qemu-block/2015-08/msg00236.html
As discussed in the previous thread, this adds a new command called
'blockdev-snapshot', that simply takes references to two existing
block devices. I decided to share most of
dovgaluk writes:
> Hi!
> Alex Bennée писал 2015-09-04 10:49:
>> * What to do about icount?
>>
>> What is the impact of multi-thread on icount? Do we need to disable it
>> for MTTCG or can it be correct per-cpu? Can it be updated lock-step?
> Why can't we have separate icount for each CPU?
> The
On Fri, Sep 04, 2015 at 01:24:11PM +0100, Peter Maydell wrote:
> This is a brief writeup of what we discussed at the QEMU Summit 2015
> at KVM Forum last month.
> * Continous integration
> * Another perennial issue :-)
> * Buildbot is broken and unmaintained: will probably go down soon
> * The
On Fri, 2015-09-04 at 12:31 +0100, Peter Maydell wrote:
> On 4 September 2015 at 12:24, Richard Purdie
> wrote:
> > So just based on that, yes, seems that the rx_fifo looks to be
> > overrunning. I can add the asserts but I think it would just confirm
> > this.
>
> Yes, the point of adding assert
> On 4 Sep 2015, at 14:38, Lluís Vilanova wrote:
>
> dovgaluk writes:
>
>> Hi!
>> Alex Bennée писал 2015-09-04 10:49:
>>> * What to do about icount?
>>>
>>> What is the impact of multi-thread on icount? Do we need to disable it
>>> for MTTCG or can it be correct per-cpu? Can it be updated loc
On 3 September 2015 at 06:27, Jonathan Neuschäfer wrote:
> Currently, __target_cmsg_nxthdr compares a pointer derived from
> target_cmsg against the msg_control field of target_msgh (through
> subtraction). This failed for me when emulating i386 code under x86_64,
> because pointers in the host a
Hi,
Perl 5.22 has deprecated unescaped { inside a regexp, which leads to
very annoying warnings. Since we use checkpatch from the Linux kernel, I
found a corresponding patch [1] that fixes it. Do we just get the new
checkpatch from the kernel, or do we integrate the patch ourself?
[1] https:
Hi Markus
On Thu, Sep 3, 2015 at 4:29 PM, Markus Armbruster wrote:
> Series is based on "[PATCH 00/26] qapi: Another round of fixes and
> cleanups" (which actually has 33 patches now). It also needs my
> "[PATCH for-2.4 0/2] qom: Fix misuse of Error API" to pass tests.
>
> You can fetch it from
Mark Burton writes:
[...]
* What to do about icount?
What is the impact of multi-thread on icount? Do we need to disable it
for MTTCG or can it be correct per-cpu? Can it be updated lock-step?
We need some input from the guys that use icount the most.
>>>
>>> That m
On 09/03/2015 02:17 AM, Richard Henderson wrote:
{
/* Sync the tb dependent flag between translate and runtime. */
-if (dc->tb_flags != dc->synced_flags) {
-tcg_gen_movi_tl(env_flags, dc->tb_flags);
+if ((dc->tb_flags ^ dc->synced_flags) & D_FLAG) {
+tcg_gen_mov
On 09/03/2015 04:44 PM, Richard Henderson wrote:
That's patch 7/17. ;-)
Woops , I just realized ;-)
R0 is not an *architectural* zero. It's a software convention. The
spec is fairly clear on this point.
I agree that there ought to be some special-casing of the software
convention, but
On Do, 2015-09-03 at 12:45 +0200, Juergen Gross wrote:
> When Xen is using the qemu usb framework for pure passthrough of I/Os
> to host devices the handling of isoc jobs is rather complicated if
> multiple isoc frames are transferred with one call.
>
> Instead of calling the framework with each f
On 09/03/2015 02:17 AM, Richard Henderson wrote:
-
-uint32_t HELPER(mul32)(CPUOpenRISCState *env,
- uint32_t ra, uint32_t rb)
-{
-uint64_t result;
-uint32_t high, cy;
-
-OpenRISCCPU *cpu = openrisc_env_get_cpu(env);
-
-result = (uint64_t)ra * rb;
-/* re
On 3 September 2015 at 00:58, Laurent Vivier wrote:
> This patch introduces a system very similar to the one used in the kernel
> to attach specific functions to a given file descriptor.
>
> In this case, we attach a specific "host_to_target()" translator to the fd
> returned by signalfd() to be a
On 31 August 2015 at 22:28, Alistair Francis
wrote:
> On Mon, Aug 31, 2015 at 1:54 PM, John Snow wrote:
>> For some reason, this patch never made it to the qemu-devel archives for
>> either v5 or v6. I only received a direct copy to my inbox, but the
>> mailer daemon seems to have dropped this pa
On 1 September 2015 at 21:27, Laurent Vivier wrote:
> This patch allows to run example given by open_by_handle_at(2):
>
> The following shell session demonstrates the use of these two programs:
>
>$ echo 'Can you please think about it?' > cecilia.txt
>$ ./t_name_to_ha
On 4 September 2015 at 12:48, Andrew Jones wrote:
> Are you also running configure (with the opposite arch selected) after
> 'make clean'? If not, then that could be the source of your problems.
> Anyway, please describe the issues you're seeing because I don't see
> what this patch is doing that
On 2 September 2015 at 16:53, Sergey Sorokin wrote:
> There is an error in arm_excp_unmasked() function:
> bitwise operator & is used with integer and bool operands
> causing an incorrect zeroed result.
> The patch fixes it.
>
> Signed-off-by: Sergey Sorokin
Applied to target-arm.next, thanks.
On 4 September 2015 at 12:48, Andrew Jones wrote:
> The lines this
> patch adds are already there. See the arm_clean target in
> config/config-arm-common.mak.
I see your point now. Maybe then "arm_clean" should be changed in
"arch_clean" in config-arm-common.mak?
Regards.
On 09/04/2015 03:55 AM, Markus Armbruster wrote:
>>> +
>>> +query-schema returns a JSON array of SchemaInfo objects. These
>>> +objects together describe the wire ABI, as defined in the QAPI schema.
>>
>> Maybe an additional sentence here, perhaps along the lines of:
>>
>> Note that the wire form
On 09/03/2015 02:17 AM, Richard Henderson wrote:
Signed-off-by: Richard Henderson
---
target-openrisc/helper.h | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
Reviewed-by: Bastian Koppelmann
On 2 September 2015 at 11:03, Sergey Sorokin wrote:
> If any store instruction writes the code inside the same TB
> after this store insn, the execution of the TB must be stopped
> to execute new code correctly.
> As described in ARMv8 manual D3.4.6 a self-modified code need to do
> IC invalidatio
On 09/03/2015 02:17 AM, Richard Henderson wrote:
True, this is unused so far, but commented out is worse than
actually implemented properly.
Signed-off-by: Richard Henderson
---
target-openrisc/int_helper.c | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-)
R
On 09/03/2015 08:30 AM, Markus Armbruster wrote:
> How many bits we use internally is an implementation detail. It could
> be pressed into external interface service as very approximate range
> information, but that's probably a bad idea. If we need range
> information, we better do it properly.
On 03/09/15 17:58, Peter Crosthwaite wrote:
Hi Mike,
On Thu, Sep 3, 2015 at 2:27 AM, GitNoviceMikeH
wrote:
From: GitNoviceMikeH
Most ARM cores switch unconditionally to ARM mode when an exception occurs;
a few (Cortex) variants have a "Thumb-exception enable" bit in the system
control regist
For RDHWR on the CP0.Count register, env->CP0_Count was being returned.
This value is a delta against the QEMU_CLOCK_VIRTUAL clock, not the
correct current value of CP0.Count. Use cpu_mips_get_count() instead.
Signed-off-by: Alex Smith
Cc: Aurelien Jarno
Cc: Leon Alrae
---
target-mips/op_helpe
Hi!
Alex Bennée писал 2015-09-04 10:49:
* What to do about icount?
What is the impact of multi-thread on icount? Do we need to disable it
for MTTCG or can it be correct per-cpu? Can it be updated lock-step?
Why can't we have separate icount for each CPU?
Then virtual timer will be assigned to
Lluís Vilanova писал 2015-09-04 16:00:
Mark Burton writes:
[...]
* What to do about icount?
What is the impact of multi-thread on icount? Do we need to disable
it
for MTTCG or can it be correct per-cpu? Can it be updated
lock-step?
We need some input from the guys that use icount the most.
On 09/03/2015 08:30 AM, Markus Armbruster wrote:
> To eliminate the temptation for clients to look up types by name
> (which are not ABI), replace all type names by meaningless strings.
>
> Reduces output of query-schema by 13 out of 85KiB.
>
> As a debugging aid, provide option -u to suppress th
On Fri, Sep 04, 2015 at 03:48:35PM +0200, Alexander Spyridakis wrote:
> On 4 September 2015 at 12:48, Andrew Jones wrote:
> > Are you also running configure (with the opposite arch selected) after
> > 'make clean'? If not, then that could be the source of your problems.
> > Anyway, please describe
On 4 September 2015 at 07:49, Pavel Fedin wrote:
> Hi! This message is mainly for Peter. I say you reviewed my major sets, but
> looks like missed this
> one. If it is OK, we could apply it, and i could successfully bring back the
> missing part in
> vGICv3-enabled hw/arm/virt.c which attaches
On 09/04/2015 06:57 AM, Marc-André Lureau wrote:
> Hi Markus
>
> On Thu, Sep 3, 2015 at 4:29 PM, Markus Armbruster wrote:
>> Series is based on "[PATCH 00/26] qapi: Another round of fixes and
>> cleanups" (which actually has 33 patches now). It also needs my
>> "[PATCH for-2.4 0/2] qom: Fix misu
On 4 September 2015 at 12:39, Pavel Fedin wrote:
> This small patchset is actually a small extraction from vGICv3 support,
> as it was suggested in
> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00921.html.
> Initially i wanted to just make a check, but ended up full implementation
> w
On 4 September 2015 at 15:05, Andrew Jones wrote:
> But anyway I would suggest you do your 'make clean' or even a
> 'make distclean' *before* running configure the second time.
> Otherwise you'll leave old object files around from the previously
> configured arch. I.e. you want 'make clean' to app
Hello!
> I think we need to leave enough space for all of GICC/GICV/GICH
> (that's 2 pages for GICC, 2 for GICV, 1 for GICH). They're optional
> in a GICv3, but we may want them for emulation later on and if we
> haven't left ourselves enough space we'll be a bit stuck.
Do we really need this?
Use c_name() instead of ad hoc code. Doesn't upcase the -p prefix,
which is an improvement in my book. Unbreaks prefix containing '.',
but other funny characters remain broken. To be fixed next.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
---
docs/qapi-code-gen.txt | 8
A flat union's tag member gets renamed to 'kind' in the generated
code. Breaks when another member named 'kind' exists.
Example, adapted from qapi-schema-test.json:
{ 'struct': 'UserDefUnionBase',
'data': { 'kind': 'str', 'enum1': 'EnumOne' } }
We generate:
struct UserDefFlatUnio
qapi-event.py breaks when you ask for a funny prefix like '@'.
Protect it.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
---
scripts/qapi.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/scripts/qapi.py b/scripts/qapi.py
index ba11c54..bc3f4d3 100644
--- a/scripts/qapi.py
gen_sync_call()'s parameter indent is useless: gen_sync_call() uses it
only as optional argument for push_indent() and pop_indent(), their
default is four, and gen_sync_call()'s only caller passes four. Drop
the parameter.
gen_visitor_input_containers_decl()'s parameter obj is always
"QOBJECT(arg
The following changes since commit b041066421e8dcc7d080dfcfd83551c9c9f24ade:
Merge remote-tracking branch 'remotes/stefanha/tags/tracing-pull-request'
into staging (2015-09-03 16:17:28 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2015-09-04
When event FOO's 'data' is a struct with a base, we consider only the
struct's direct members, and ignore its base. The generated
qapi_event_send_foo() doesn't take arguments for base members.
No such events currently exist in the QMP schema.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric B
The guards around built-in declarations lose their _H. It never made
much sense anyway.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
---
scripts/qapi.py | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/scripts/qapi.py b/scripts/qapi.py
index e656beb..b
We generate a declaration, but no definition.
The QMP schema has two: Qcow2OverlapChecks and BlockdevRef. Neither
visit_type_Qcow2OverlapChecksKind() nor visit_type_BlockdevRefKind()
is actually used.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
---
tests/qapi-schema/qapi-schema-t
1 - 100 of 327 matches
Mail list logo
