On 12/10/2016 01:51, Taylor Edward Heimbichner wrote:
> I'm writing to ask if any executable that you use to test QEMU
> systematically tests all, or at least a large portion, of the x86
> instruction set? We're working on a project that involves dynamic taint
> analysis and would like to use an
From: Li Qiang
In v9fs_link dispatch function, it doesn't put the 'oldfidp'
fid object, this will make the 'oldfidp->ref' never reach to 0,
thus leading a memory leak issue. This patch fix this.
Signed-off-by: Li Qiang
---
hw/9pfs/9p.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/9pf
This was found with test-i386. The issue is that instructions
such as
addr32 lea (%eax), %rax
did not perform a 32-bit extension, because the LEA translation
skipped the gen_lea_v_seg step. That step does not just add
segments, it also takes care of extending from address size to
pointer si
> -Original Message-
> From: Michael Tokarev [mailto:m...@tls.msk.ru]
> Sent: Wednesday, October 12, 2016 2:46 PM
> Subject: Re: [PATCH] mmap-alloc: check before use for ptr pointer
>
> 12.10.2016 05:05, Gonglei wrote:
> > If ptr mmap failed, we don't need to do a superfluous
> > calculati
On 12/10/2016 09:37, Gonglei (Arei) wrote:
>> -Original Message-
>> From: Michael Tokarev [mailto:m...@tls.msk.ru]
>> Sent: Wednesday, October 12, 2016 2:46 PM
>> Subject: Re: [PATCH] mmap-alloc: check before use for ptr pointer
>>
>> 12.10.2016 05:05, Gonglei wrote:
>>> If ptr mmap faile
On Fri, Oct 07, 2016 at 02:51:17PM +0100, Daniel P. Berrange wrote:
> The bsd-user/linux-user programs make use of the CPU emulation
> code and this now requires that the trace events subsystem
> is enabled, otherwise it'll crash trying to allocate an empty
> trace events bitmap for the CPU object.
> -Original Message-
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Wednesday, October 12, 2016 3:41 PM
> To: Gonglei (Arei); Michael Tokarev; qemu-devel@nongnu.org
> Cc: qemu-triv...@nongnu.org; Herongguang (Stephen)
> Subject: Re: [PATCH] mmap
On 12/10/2016 06:44, David Gibson wrote:
> The libqos code for accessing PCI on the spapr machine type uses IOBASE()
> and MMIOBASE() macros to determine the address in the CPU memory map of
> the windows to PCI address space.
>
> This is a detail of the implementation of PCI in the machine type
On 12/10/2016 06:44, David Gibson wrote:
> In pci-spapr.c (as in pci-pc.c from which it was derived), the
> pci_hole_start/pci_hole_size and pci_iohole_start/pci_iohole_size pairs[1]
> essentially define the region of PCI (not CPU) addresses in which MMIO
> or PIO BARs respectively will be alloca
"Daniel P. Berrange" writes:
> Instead of requiring all callers to go through the mutli-step
multi-step
> process of turning QemuOpts into a suitable QObject for visiting,
> add a new constructor that encapsulates this logic. This will
> allow QObjectInputVisitor to be a drop-in replacement for
On Tue, Oct 11, 2016 at 1:07 PM, Ashijeet Acharya
wrote:
> This series adds blockdev-add support for SSH block driver.
>
> Patch 1 prepares the code for the addition of a new option prefix,
> which is "server.". This is accomplished by adding a
> ssh_has_filename_options_conflict() function which
On 12/10/2016 07:58, P J P wrote:
> From: Prasad J Pandit
>
> 16550A UART device uses an oscillator to generate frequencies
> (baud base), which decide communication speed. This speed could
> be changed by dividing it by a divider. If the divider is
> greater than the baud base, speed is set to
On 12/10/2016 09:54, Gonglei (Arei) wrote:
>
>> -Original Message-
>> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
>> Bonzini
>> Sent: Wednesday, October 12, 2016 3:41 PM
>> To: Gonglei (Arei); Michael Tokarev; qemu-devel@nongnu.org
>> Cc: qemu-triv...@nongnu.o
On 12/10/2016 06:44, David Gibson wrote:
> Currently the functions in pci-spapr.c (like pci-pc.c on which it's based)
> don't distinguish between 32-bit and 64-bit PCI MMIO. At the moment, the
> qemu side implementation is a bit weird and has a single MMIO window
> straddling 32-bit and 64-bit r
Am 12.10.2016 um 10:09 hat Ashijeet Acharya geschrieben:
> I received a mail saying my series failed the automatic build test but
> it builds completely fine (after applying Dan's patch obviously) in my
> local environment.
The reason why patchew fails to build your series is because it doesn't
un
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/7] Improve PCI IO window orgnaization for pseries
Message-id: 1476246592-24228-1-git-send-email-da...@gibson.dropbear.id.au
Type: series
=== TEST SCRIPT BEGIN ===
#!/bi
On 10/11/2016 07:49 PM, Igor Mammedov wrote:
On Mon, 10 Oct 2016 21:09:30 +0800
Xiao Guangrong wrote:
On 10/10/2016 08:51 PM, Igor Mammedov wrote:
On Sat, 8 Oct 2016 15:17:14 +0800
Xiao Guangrong wrote:
On 09/30/2016 09:14 PM, Igor Mammedov wrote:
On Fri, 12 Aug 2016 14:54:05 +0800
Xiao
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Message-id: 1476247497-6976-1-git-send-email-da...@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCHv2 0/7] Improve PCI IO window orgnaization for
pseries
Type: series
=== TEST SCRIPT BEGIN ===
#!/
On Wed, Oct 12, 2016 at 1:52 PM, Kevin Wolf wrote:
> Am 12.10.2016 um 10:09 hat Ashijeet Acharya geschrieben:
> Of course, we must be able to build qemu correctly both with ssh enabled
> and disabled, so if you can indeed see a (different) build error with
> disabled libssh2, that needs to be fix
> From: Kirti Wankhede
> Sent: Tuesday, October 11, 2016 4:29 AM
>
[...]
> +
> +/*
> + * mdev_unregister_device : Unregister a parent device
> + * @dev: device structure representing parent device.
> + *
> + * Remove device from list of registered parent devices. Give a chance to
> free
> + * ex
Am 12.10.2016 um 03:14 hat Fam Zheng geschrieben:
> On Wed, 09/28 15:04, Fam Zheng wrote:
> > Handling this is similar to what is done to the L2 entry in the case of
> > compressed clusters.
>
> Kevin, Max, is there anything else I need to do before this patch can be
> applied?
Hm, actually, it l
Am 12.10.2016 um 10:37 hat Ashijeet Acharya geschrieben:
> On Wed, Oct 12, 2016 at 1:52 PM, Kevin Wolf wrote:
> > Am 12.10.2016 um 10:09 hat Ashijeet Acharya geschrieben:
>
> > Of course, we must be able to build qemu correctly both with ssh enabled
> > and disabled, so if you can indeed see a (d
> I received a mail saying my series failed the automatic build test but
> it builds completely fine (after applying Dan's patch obviously) in my
> local environment.
>
> Going through the config output of the test script, I see that the
> supporting library for SSH which is "libssh2" seems to be d
Paolo Bonzini writes:
> There is a data race if the variable is written concurrently to the
> read. In C11 this has undefined behavior. Use atomic_read. The
> write side does not need atomic_set, because it is protected by a
> mutex.
>
> Signed-off-by: Paolo Bonzini
Reviewed-by: Alex Bennée
* Markus Armbruster (arm...@redhat.com) wrote:
> Marc-André Lureau writes:
>
> > This option does nothing since commit 06ac27f. Deprecate it.
> >
> > Signed-off-by: Marc-André Lureau
> > ---
> > vl.c | 11 +++
> > include/monitor/monitor.h | 2 +-
> > qemu-options
From: "Daniel P. Berrange"
The colo patch series added various trace events to the top
level trace-events file, despite the files using them being
in a sub-dir.
commit 30656b097e9dd7978d3fe9416cb9f5a421a9e63e
Author: Zhang Chen
Date: Tue Sep 27 10:22:34 2016 +0800
filter-rewriter:
From: "Daniel P. Berrange"
If the ftrace backend is compiled into QEMU, any attempt
to start QEMU while non-root will fail due to the
inability to open /sys/kernel/debug/tracing/tracing_on.
Add a fallback into the code so that it connects up the
trace_marker_fd variable to /dev/null when getting
The following changes since commit 627eae7d729277c84f8e0ac07a8caab39c92c38d:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging
(2016-10-10 16:23:40 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/tracing-pull-request
for you to
From: "Daniel P. Berrange"
Currently methods which want to iterate over trace events,
do so using the trace_event_count() and trace_event_id()
methods. This leaks the concept of a single ID enum to
the callers. There is an alternative trace_event_pattern()
method which can be used in an iteration
From: "Daniel P. Berrange"
This converts the HMP/QMP monitor API implementations
and some internal trace control methods to use the new
trace event iterator APIs.
Reviewed-by: Stefan Hajnoczi
Signed-off-by: Daniel P. Berrange
Reviewed-by: Lluís Vilanova
Message-id: 1475588159-30598-5-git-send
From: "Daniel P. Berrange"
The CPUState struct has a bitmap tracking which VCPU
events are currently active. This is indexed based on
the event ID values, and sized according the maximum
TraceEventVCPUID enum value.
When we start dynamically assigning IDs at runtime,
we can't statically declare
From: "Daniel P. Berrange"
Instead of having a global dstate array, declare a single
'uint16 TRACE_${EVENT_NAME}_DSTATE' variable for each
trace event. Record a pointer to this variable in the
TraceEvent struct too.
By turning trace_event_get_state_dynamic_by_id into a
macro, this still hits the
From: "Daniel P. Berrange"
The format/h.py file adds an include for control.h to
generated-tracers.h. ftrace, log and syslog, then
add more duplicate includes for control.h.
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Lluís Vilanova
Signed-off-by: Daniel P. Berrange
Message-id: 1475588159-30598
From: "Daniel P. Berrange"
The trace_event_count, trace_event_id and
trace_event_pattern methods are no longer required
now that everything is using the iterator APIs
The trace_event_set_state and trace_event_set_vcpu_state
macros were also unused.
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Llu
From: "Daniel P. Berrange"
Instead of having the code generator assign event IDs and
event VCPU IDs, assign them when the events are registered
at runtime. This will allow code to be generated from
individual trace-events without having to figure out
globally unique numbering at build time.
Revi
From: "Daniel P. Berrange"
Currently simpletrace assumes that events are given IDs
starting from 0, based on the order in which they appear
in the trace-events file, with no gaps. When the
trace-events file is split up, this assumption becomes
problematic.
To deal with this, extend the simpletra
From: "Daniel P. Berrange"
Currently we only expose a TraceEvent array, which must
be indexed via the TraceEventID enum constants. This
changes the generator to expose a named TraceEvent
instance for each event, with an _EVENT suffix.
Reviewed-by: Lluís Vilanova
Reviewed-by: Stefan Hajnoczi
Si
From: "Daniel P. Berrange"
Currently event-internal.h includes generated-events.h,
while generated-events.h includes event-internal.h
causing a circular dependency.
event-internal.h requires that the content of
generated-events.h comes first, so that it can see
the typedefs for TraceEventID and
From: Lluís Vilanova
Add missing execution mode documentation for the 'guest_cpu_enter' and
'guest_cpu_reset' events.
Signed-off-by: Lluís Vilanova
Message-id: 147566900921.7708.656450813307396468.st...@fimbulvetr.bsc.es
Signed-off-by: Stefan Hajnoczi
---
trace-events | 2 ++
1 file changed,
From: "Daniel P. Berrange"
Remove the notion of there being a single global array
of trace events, by introducing a method for registering
groups of events.
The module_call_init() needs to be invoked at the start
of any program that wants to make use of the trace
support. Currently this covers s
From: "Daniel P. Berrange"
The TraceEventID and TraceEventVCPUID enums constants are
no longer actually used for anything critical.
The TRACE_EVENT_COUNT limit is used to determine the size
of the TraceEvents array, and can be removed if we just
NULL terminate the array instead.
The TRACE_VCPU_
From: "Daniel P. Berrange"
Instead of reading the contents of 'trace-events' from stdin,
accept the filename as a positional parameter. This also
allows for reading from multiple files, though this facility
is not used at this time.
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Lluís Vilanova
Sign
On 10/11/2016 12:24 PM, David Gibson wrote:
> On Mon, Oct 10, 2016 at 02:56:25PM +0200, Cédric Le Goater wrote:
>>
@@ -227,11 +227,44 @@ static void ppc_powernv_init(MachineState *machine)
snprintf(chip_name, sizeof(chip_name), "chip[%d]", CHIP_HWID(i));
object_prop
From: "Daniel P. Berrange"
Currently the generated-events.[ch] files contain the
event dstates, constants and TraceEvent structs, while the
generated-tracers.[ch] files contain the actual trace
probe logic. With the removal of usage of the event enums
from the API there is no longer any compellin
From: "Daniel P. Berrange"
The declarations in the generated-tracers.h file are
assuming there's only ever going to be one instance
of this header, as they are not namespaced. When we
have one header per event group, if a single source
file needs to include multiple sets of trace events,
the symb
From: "Daniel P. Berrange"
The _read_events method is used by callers outside of
its module, so should be a public method, not private.
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Lluís Vilanova
Signed-off-by: Daniel P. Berrange
Message-id: 1475588159-30598-18-git-send-email-berra...@redhat.com
From: Prasad J Pandit
Rocker network switch emulator has test registers to help debug
DMA operations. While testing host DMA access, a buffer address
is written to register 'TEST_DMA_ADDR' and its size is written to
register 'TEST_DMA_SIZE'. When performing TEST_DMA_CTRL_INVERT
test, if DMA buffe
From: "Daniel P. Berrange"
Move the reading of events out of the 'tracetool.generate'
method and into tracetool.main, so that the latter is not
tied to generating from a single source of events.
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Lluís Vilanova
Signed-off-by: Daniel P. Berrange
Message
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v1 0/3] POWER9 TCG enablements - part6
Message-id: 1476248933-25562-1-git-send-email-nik...@linux.vnet.ibm.com
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=ba
Hi Pranith,
I was curious about the status of your MTTCG GSoC work:
I saw your fence series which implements the noop memory barrier/fence
instructions on various architectures, but I wasn't sure if that also
covers the case where a strong target is emulated on a weak host.
Did you make TCG autom
Am 11.10.2016 um 18:50 hat Markus Armbruster geschrieben:
> Eric Blake writes:
>
> > On 10/11/2016 09:57 AM, Kevin Wolf wrote:
> >> Should we introduce a new, clean blockdev-stream command that fixes this
> >> and matches the common name pattern? Of course, block-stream vs.
> >> blockdev-stream c
On 11 October 2016 at 16:51, Taylor Edward Heimbichner
wrote:
> I'm a student researcher with the University of Arizona's Computer Science
> Department. I'm writing to ask if any executable that you use to test QEMU
> systematically tests all, or at least a large portion, of the x86
> instruction
Max,
Just a common question for this case, if sshx block driver wasn't built
into qemu-img, this case would fail as below:
exec /home/haoqf/KVMonz/qemu/tests/qemu-iotests/../../qemu-img info
--image-opts driver=ssh,host=localhost,port=0.42,path=/foo
qemu-img: Could not open
'driver=ssh,host=
Paolo Bonzini writes:
> Do not use the somewhat mysterious atomic_mb_read/atomic_mb_set,
> instead make sure that the operations on QemuEvent are annotated
> with the desired acquire and release semantics.
>
> In particular, qemu_event_set wakes up the waiting thread, so it must
> be a release f
Yes it did.
** 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/1319100
Title:
qemu-arm-static bug in signal handling causes mono and ja
On Tue 11 Oct 2016 06:50:27 PM CEST, Markus Armbruster wrote:
> * Is the extended command still a sane interface? If writing clear
> documentation for it is hard, it perhaps isn't. Pay special
> attention to failure modes. Overloaded arguments are prone to
> confusing errors.
This is wha
Hi
On Tue, Oct 11, 2016 at 8:44 PM Daniel P. Berrange
wrote:
>
> Not sure if this is immediately helpful to your scneario or
> not, but I'd like to see the qemu_chr_add_handlers method
> removed long term, and everything converted to use the
> qemu_chr_fe_add_watch function instead. This reverse
On Tue 11 Oct 2016 06:32:39 PM CEST, Markus Armbruster wrote:
>>> 3) QEMU could advertise that feature to the client. This is probably
>>> simpler than trying to figure it out from the API. I guess that's
>>> the idea of 'qmp_capabilities'?
>>
>> I think that was the idea, though it was never used
"Daniel P. Berrange" writes:
> When converting QemuOpts to a QObject, there is no information
> about compound types available,
Yes, that's a drawback of splitting the conversion into a QemuOpts ->
QObject part that is oblivious of types, and a QObject -> QAPI object
part that knows the types.
Paolo Bonzini writes:
> This introduces load-acquire and store-release operations in QEMU.
> For now, just use them as an implementation detail of atomic_mb_read
> and atomic_mb_set.
>
> Since docs/atomics.txt documents that atomic_mb_read only synchronizes
> with an atomic_mb_set of the same va
On 12/10/2016 06:44, David Gibson wrote:
> The 'spapr-pci-host-bridge' represents the virtual PCI host bridge (PHB)
> for a PAPR guest. Unlike on x86, it's routine on Power (both bare metal
> and PAPR guests) to have numerous independent PHBs, each controlling a
> separate PCI domain.
>
> There
On 12/10/2016 11:28, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> This introduces load-acquire and store-release operations in QEMU.
>> For now, just use them as an implementation detail of atomic_mb_read
>> and atomic_mb_set.
>>
>> Since docs/atomics.txt documents that atomic_mb_read onl
On Tue, 10/11 15:27, Kevin Wolf wrote:
> Now that QAPI supports boxed types, we can have unions at the top level
> of a command, so let's put our real options directly there for
> blockdev-add instead of having a single "options" dict that contains the
> real arguments.
>
> blockdev-add is still e
On 12/10/2016 11:21, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> Do not use the somewhat mysterious atomic_mb_read/atomic_mb_set,
>> instead make sure that the operations on QemuEvent are annotated
>> with the desired acquire and release semantics.
>>
>> In particular, qemu_event_set wak
Am 11.10.2016 um 18:45 hat Paolo Bonzini geschrieben:
> > I think my point was that you don't have to count requests at the BB
> > level if you know that there are no requests pending on the BB level
> > that haven't reached the BDS level yet.
>
> I need to count requests at the BB level because t
Wed, Oct 12, 2016 at 11:10:55AM CEST, ppan...@redhat.com wrote:
>From: Prasad J Pandit
>
>Rocker network switch emulator has test registers to help debug
>DMA operations. While testing host DMA access, a buffer address
>is written to register 'TEST_DMA_ADDR' and its size is written to
>register 'T
The files w/cpu/a*mpcore.c are already assigned to the ARM CPU
section, but the corresponding headers include/hw/cpu/a*mpcore.h
are still missing.
The file hw/*/imx* are already assigned to the i.MX31 machine, but
the corresponding header files include/hw/*/imx* are still missing.
The file hw/mis
On 6 October 2016 at 11:59, Peter Maydell wrote:
> On 5 October 2016 at 14:44, Juan Quintela wrote:
>> From: Juan Quintela
>>
>> The following changes since commit bbc4c3f4f3c624e2de64fdcb79f4dd8c1a508e9d:
>>
>> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into
>> staging (2
On 12/10/2016 06:44, David Gibson wrote:
> Currently the default PCI host bridge for the 'pseries' machine type is
> constructed with its IO windows in the 1TiB..(1TiB + 64GiB) range in
> guest memory space. This means that if > 1TiB of guest RAM is specified,
> the RAM will collide with the PCI
NBD is using the CoMutex in a way that wasn't anticipated. For example, if
there are
N(N=26, MAX_NBD_REQUESTS=16) nbd write requests, so we will invoke
nbd_client_co_pwritev
N times.
time request Actions
1
On 12/10/2016 11:50, Kevin Wolf wrote:
> > (By the way, I need to repost this series anyway, but let's finish the
> > discussion first to understand what you'd like to have in 2.8).
>
> I'm still not completely sold on the order in which we should do things,
> but you've been insisting enough tha
Am 11.10.2016 um 17:47 hat John Snow geschrieben:
> On 10/10/2016 03:23 PM, Mark Cave-Ayland wrote:
> >On 10/10/16 17:34, Eric Blake wrote:
> >
> >>On 10/09/2016 11:43 AM, Mark Cave-Ayland wrote:
> >>>The hard-coded default alignment is BDRV_SECTOR_SIZE, however this is not
> >>>necessarily the cas
On 10/12/2016 06:18 PM, Changlong Xie wrote:
time request Actions
29 15(most case) in_flight=15, Coroutine=C15, free_sema->holder=C17,
mutex->locked=false
On 10/11/2016 08:32 PM, Igor Mammedov wrote:
Of course, @fit and @current_number should be persistent during live migration.
you can drop RCU and @current_number,
and @fit could be exactly recreated on target side from
-device nvdim ...
set of options, which must include all currently prese
> From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
> Sent: Tuesday, October 11, 2016 4:29 AM
>
[...]
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 2ba19424e4a1..ce6d6dcbd9a8 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Wednesday, October 12, 2016 6:07 AM
> > @@ -696,6 +1067,11 @@ static int vfio_iommu_replay(struct vfio_iommu *iommu,
> >
> > iova += size;
> > }
> > +
> > + if (!dma->iommu_mapped) {
> > +
Hi all,
I spent some time cleaning up the wiki in order to make it easier to
organize information.
The pages are now organized in a mostly hierarchical fashion, starting
at the following entry points:
* http://qemu-project.org/ChangeLog
* http://qemu-project.org/Contribute (formerly /Contribute/
On 23/09/2016 19:43, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Add the rest of the APIC state to the 'info lapic' dump,
> since it is of course state that wasn't printed that I'd
> messed up.
>
> You now have output like:
>
> (qemu) info lapic
> dumping local AP
On 12/10/2016 12:18, Changlong Xie wrote:
> +if (s->in_flight == MAX_NBD_REQUESTS) {
> +qemu_co_queue_wait(&s->free_sema);
> assert(s->in_flight < MAX_NBD_REQUESTS);
> }
I was wondering if this should be a while loop instead, but the
assertion protects against that. So
On 11/10/2016 20:41, Anand J wrote:
> I want to run KVM on qemu. For this qemu must provide vt-x/amd-v
> instruction support in the software mode.
> I was planning to try to add this feature in qemu. If somebody is already
> working on it please reply.
QEMU provides AMD-V support.
Paolo
On 09/10/2016 21:50, Emil Condrea wrote:
> On Tue, Oct 4, 2016 at 11:06 AM, Paolo Bonzini wrote:
>>
>>
>> On 04/10/2016 08:43, Emil Condrea wrote:
>>> xen_be_frontend_changed -> xen_fe_frontend_changed
>>
>> This is not correct. The front-end is implemented in the guest domain,
>> while the bac
On Wed, Oct 12, 2016 at 12:07:50PM +0200, Laurent Vivier wrote:
>
>
> On 12/10/2016 06:44, David Gibson wrote:
> > Currently the default PCI host bridge for the 'pseries' machine type is
> > constructed with its IO windows in the 1TiB..(1TiB + 64GiB) range in
> > guest memory space. This means t
On 01.10.2016 01:00, John Snow wrote:
Cleaning up after we have deferred to the main thread but before the
transaction has converged can be dangerous and result in deadlocks
if the job cleanup invokes any BH polling loops.
A job may attempt to begin cleaning up, but may induce another job to
ent
On 12 October 2016 at 09:47, Stefan Hajnoczi wrote:
> The following changes since commit 627eae7d729277c84f8e0ac07a8caab39c92c38d:
>
> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging
> (2016-10-10 16:23:40 +0100)
>
> are available in the git repository at:
>
> git://
On Tue, Oct 11, 2016 at 5:08 PM, Richard Henderson wrote:
> On 10/11/2016 08:51 AM, Artyom Tarasenko wrote:
>>
>> On Tue, Oct 11, 2016 at 7:50 AM, Richard Henderson
>> wrote:
>>>
>>> On 10/10/2016 04:45 PM, Artyom Tarasenko wrote:
>
>
> Hmm. Would it make more sense to reorg these as
On Tue, 11 Oct 2016 16:06:55 +0200
Thomas Huth wrote:
> On 11.10.2016 15:55, Greg Kurz wrote:
> > On Tue, 11 Oct 2016 15:32:02 +0200
> > Thomas Huth wrote:
> >
> >> The pxe-test is run for three different targets now (x86_64, i386
> >> and ppc64), and the bios-tables-test is run for two targe
it is almost a duplication of test_transaction_failure, I think it would
be better to make separate do_test_transaction_failure with parameter
and two wrappers
On 01.10.2016 01:00, John Snow wrote:
Add a regression test for the case found by Vladimir.
Reported-by: Vladimir Sementsov-Ogievskiy
On Tue, Oct 11, 2016 at 4:43 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> Remove the Niagara stub implementation from sun4u.c and add a machine,
>> compatible with Legion simulator from the OpenSPARC T1 project.
>>
>> The machine uses the firmware supplied w
On Tue, Oct 11, 2016 at 4:31 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> +sun4u_tte = TTE_PA(sun4v_tte) | (sun4v_tte & TTE_VALID_BIT);
>> +sun4u_tte |= (sun4v_tte & 3ULL) << 61;
>> +sun4u_tte |= (sun4v_tte & TTE_NFO_BIT_UA2005) >> 2;
>> +sun
Paolo Bonzini writes:
> See each patch. My attempt at fixing whatever I did when I obviously
> didn't know enough^W about the C11 memory model, and at setting a
> better example for future generations...
Have you had a chance to check up on any of the errors "make check"
throws up with the san
ping
For now there are some notes mostly about accessory patches. What about
migration itself? Is it ok?
On 16.08.2016 13:25, Vladimir Sementsov-Ogievskiy wrote:
v2:
some bugs fixed, iotests a bit changed and merged into one test.
based on block-next (https://github.com/XanClic/qemu/commits/b
On 12/10/2016 13:32, Alex Bennée wrote:
> > See each patch. My attempt at fixing whatever I did when I obviously
> > didn't know enough^W about the C11 memory model, and at setting a
> > better example for future generations...
>
> Have you had a chance to check up on any of the errors "make ch
On Mon, Oct 10, 2016 at 11:41 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> Signed-off-by: Artyom Tarasenko
>> ---
>> target-sparc/cpu.h | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/target-sparc/cpu.h b/target-sparc/cpu.
On 07.10.2016 22:28, Max Reitz wrote:
On 30.09.2016 12:53, Vladimir Sementsov-Ogievskiy wrote:
New field BdrvDirtyBitmap.persistent means, that bitmap should be saved
on bdrv_close, using format driver. Format driver should maintain bitmap
storing.
Signed-off-by: Vladimir Sementsov-Ogievskiy
-
Thanks for replying. Can you please tell me where should I start looking at
the code
in order to understand the implementation?
Thanks,
Anand
On Wed, Oct 12, 2016 at 4:27 PM, Paolo Bonzini wrote:
>
>
> On 11/10/2016 20:41, Anand J wrote:
> > I want to run KVM on qemu. For this qemu must provide
On 12/10/2016 13:34, Anand J wrote:
> Thanks for replying. Can you please tell me where should I start looking
> at the code in order to understand the implementation?
My immediate answer is that if you cannot find it, you'll have a hard
time understanding the implementation. But anyway it's in
From: Aleksandar Markovic
v1 -> v2:
- Added patches 1 and 2.
- Omitted patch on sysfs(); this patch will be treated separately,
as it is not Mips-specific, and logicaly does not belong to this
series; it will be sent at later time.
This is just a set of several Qemu Linux us
From: Aleksandar Markovic
Update linux-user/mips/termbits.h with ioctl definitions from kernel
file arch/mips/include/uapi/asm/ioctls.h.
Signed-off-by: Aleksandar Markovic
---
linux-user/mips/termbits.h | 12
1 file changed, 12 insertions(+)
diff --git a/linux-user/mips/termbits.
From: Aleksandar Markovic
Update from kernel header arch/mips/include/uqapi/asm/unistd.h.
Signed-off-by: Aleksandar Markovic
---
linux-user/mips/syscall_nr.h | 3 +++
linux-user/mips64/syscall_nr.h | 7 +++
2 files changed, 10 insertions(+)
diff --git a/linux-user/mips/syscall_nr.h b/li
From: Aleksandar Markovic
By looking at the file arch/mips/kernel/sys.S in Linux kernel,
it can be deduced that, for Mips32 platform, syscall
corresponding to number _NR_fadvise64 translates to kernel
function sys_fadvise64_64, and that argument layout is as
follows:
0 32 0
1 - 100 of 355 matches
Mail list logo
