From: Pavel Butsykin
The table info(information about the system state) closes earlier
and some of its elements are outside(trace-events, rocker, etc). This
can be confusing and lead to additional bugs.
Signed-off-by: Pavel Butsykin
Signed-off-by: Denis V. Lunev
CC: Luiz Capitulino
CC: Paolo
From: Pavel Butsykin
It will be easier if you need to add info-commands to edit
only hmp-commands-info.hx, before this had to edit monitor.c and
hmp-commands.hx
Signed-off-by: Pavel Butsykin
Signed-off-by: Denis V. Lunev
CC: Luiz Capitulino
CC: Paolo Bonzini
CC: Peter Maydell
---
.gitignor
The monivation of this set is simple. Recently we have proposed patch
to monitor.c with specific x86 APIC HMP commands. The patchset was denied
with the main motivation "No more arch specific code in monitor.c"
This patchset is the first step to move arch specific code from
monitor.c targets.
So,
From: Pavel Butsykin
For moving target- and device-specific code from monitor.c,
to beginning we move info_cmds content to hmp-commands-info.hx
Signed-off-by: Pavel Butsykin
Signed-off-by: Denis V. Lunev
CC: Luiz Capitulino
CC: Paolo Bonzini
CC: Peter Maydell
---
Makefile.target |
From: Pavel Butsykin
Move target-specific code out of /monitor.c to /target-*/monitor.c,
this will avoid code cluttering and using random ifdeffery. The solution
is quite simple, but solves the issue of the separation of target-specific
code from monitor
The stub version API target_monitor_defs
On Tue, 2015-09-08 at 12:09 +0530, Bharata B Rao wrote:
> On Tue, Sep 08, 2015 at 04:08:06PM +1000, Michael Ellerman wrote:
> > On Wed, 2015-08-12 at 10:53 +0530, Bharata B Rao wrote:
> > > On Tue, Aug 11, 2015 at 03:48:26PM +0200, Andrea Arcangeli wrote:
> > > > Hello Bharata,
> > > >
> > > > On
Veres Lajos writes:
> Hi,
>
> Please find attached a couple of typo fixes, mostly in comments/docs.
> (Please cc me directly, I am not on the list.)
>
> Best regards,
Thanks. Next time, please follow
http://qemu-project.org/Contribute/SubmitAPatch
to produce a patch in the orthodox format.
On 09/07/2015 04:21 PM, Cornelia Huck wrote:
> On Mon, 7 Sep 2015 15:39:59 +0800
> Jason Wang wrote:
>
>> > On 09/02/2015 07:06 PM, Cornelia Huck wrote:
>>> > > On Wed, 2 Sep 2015 11:25:21 +0800
>>> > > Jason Wang wrote:
> >> +static int get_extra_state(QEMUFile *f, void *pv, size_t size)
Quote from Michael:
We really should rename VHOST_RESET_OWNER to VHOST_RESET_DEVICE.
Suggested-by: Michael S. Tsirkin
Signed-off-by: Yuanhan Liu
---
docs/specs/vhost-user.txt | 4 ++--
hw/net/vhost_net.c | 2 +-
hw/virtio/vhost-user.c | 6 +++---
linux-headers/linux/vhost.h
Hi,
Here is the updated patch set for enabling vhost-user multiple queue.
This patch set introduces 2 more vhost user messages: VHOST_USER_GET_QUEUE_NUM,
for querying how many queues the backend supports, and
VHOST_USER_SET_VRING_FLAG,
for enabling/disabling a specific virt queue.
Both of th t
So that we could let vhost_user_call to handle extented requests,
such as VHOST_USER_GET/SET_PROTOCOL_FEATURES, instead of invoking
vhost_user_read/write and constructing the msg again by ourself.
Signed-off-by: Yuanhan Liu
---
hw/virtio/vhost-user.c | 37 +
1
From: "Michael S. Tsirkin"
Support a separate bitmask for vhost-user protocol features,
and messages to get/set protocol features.
Invoke them at init.
No features are defined yet.
v2: leverage vhost_user_call for request handling -- Yuanhan Liu
Signed-off-by: Michael S. Tsirkin
Signed-off-b
From: Ouyang Changchun
This patch is initially based a patch from Nikolay Nikolaev.
Here is the latest version for adding vhost-user multiple queue support,
by creating a nc and vhost_net pair for each queue.
What differs from last version is that this patch addresses two major
concerns from Mi
This is for querying how many queues the backend supports if it has mq
support(when VHOST_USER_PROTOCOL_F_MQ flag is set from the quried
protocol features).
vhost_net_get_max_queues() is the interface to export that value, and
to tell if the backend supports # of queues user requested, which is
do
So that we could use the `vq_index' as well in the vhost_net_init
stage, which is required when adding vhost-user multiple-queue support,
where we need the vq_index to indicate which queue pair we are gonna
initiate.
vhost-user has no multiple queue support yet, hence no queue_index set
before. He
From: Changchun Ouyang
Add a new message, VHOST_USER_SET_VRING_FLAG, to enable and disable
a specific virt queue, which is similar to attach/detach queue for
tap device.
virtio driver on guest doesn't have to use max virt queue pair, it
could enable any number of virt queue ranging from 1 to max
On Mon, 7 Sep 2015 13:33:56 +0200
Pierre Morel wrote:
> Let dataplane allocate different region for the desc/avail/used
> ring regions.
> Take VIRTIO_RING_F_EVENT_IDX into account to increase the used/avail
> rings accordingly.
>
> Signed-off-by: Pierre Morel
> (changed __virtio16 into uint16_
From: Raushaniya Maksudova
In some cases one needs to pause and resume a Virtual Machine from inside
of Qemu. Currently there are request functions to pause VM (vmstop), but
there are no respective ones to resume VM.
Signed-off-by: Raushaniya Maksudova
Signed-off-by: Denis V. Lunev
CC: Stefan
Description of the problem:
Client and server interacts via Network File System (NFS) or using other
network storage like CEPH. The server contains an image of the Virtual
Machine (VM) with Linux inside. The disk is exposed as SATA or IDE
to VM. VM is started on the client as usual. In the case of
From: Raushaniya Maksudova
If disk-deadlines option is enabled for a drive, one controls time
completion of this drive's requests. The method is as follows (further
assume that this option is enabled).
Every drive has its own red-black tree for keeping its requests.
Expiration time of the reques
From: Raushaniya Maksudova
Signed-off-by: Raushaniya Maksudova
Signed-off-by: Denis V. Lunev
CC: Stefan Hajnoczi
CC: Kevin Wolf
CC: Paolo Bonzini
---
include/qemu/atomic.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/qemu/atomic.h b/include/qemu/atomic.h
index bd2c075..d26
From: Raushaniya Maksudova
This patch adds per-drive option disk-deadlines.
If it is enabled, one tracks which disk'requests were not completed in time.
By default it is unset.
Signed-off-by: Raushaniya Maksudova
Signed-off-by: Denis V. Lunev
CC: Stefan Hajnoczi
CC: Kevin Wolf
CC: Markus Arm
From: Raushaniya Maksudova
This patch adds "info disk-deadlines" qemu-monitor option that prints
dump of all disk requests which caused a disk deadline in Guest OS
from the very start of Virtual Machine:
disk_id type size total_timestart_time
.--
On 7 September 2015 at 22:31, Rita Sinha wrote:
> Hi Jan,
>
> I am interested in participating in next round of Outreachy program
> with AMD IOMMU emulation project.
>
>
> I have worked on BIOS projects which includes coreboot SeaBios etc and
> bootloaders like u-boot and grub. I have experience o
On 8 September 2015 at 06:18, Richard Henderson wrote:
> On 09/07/2015 10:31 AM, Peter Maydell wrote:
>>>
>>> -if (cond < 0x0e) { /* continue */
>>> -gen_set_label(label_continue);
>>> +/* If COND was false, force the flags to #nzcv.
>>> + Note that T1 = (COND ? 0 : -1), T2 =
On 7 September 2015 at 16:45, Markus Armbruster wrote:
> A feature new in Python 2.7 crept into commit 77e703b: re.subn()'s
> fifth argument. Avoid that, use re.compile().
>
> Reported-by: Laurent Desnogues
> Signed-off-by: Markus Armbruster
Should we cc: stable on this?
thanks
-- PMM
On 7 September 2015 at 22:45, Veres Lajos wrote:
> Hi,
>
> Please find attached a couple of typo fixes, mostly in comments/docs.
> (Please cc me directly, I am not on the list.)
That patch includes at least one change to linux-headers/,
which is definitely wrong. Typos in the kernel headers need
Hello!
> We also need to update the ACPI table generation code, otherwise
> we will be instantiating a system with a GICv3 and claiming
> in the ACPI tables that it is a GICv2.
I have done everything except this piece. Where can i get any documentation on
how to describe GICv3 in MADT?
Kind r
On 8 September 2015 at 06:09, Richard Henderson wrote:
> On 09/07/2015 10:09 AM, Peter Maydell wrote:
>>
>> On 2 September 2015 at 18:57, Richard Henderson wrote:
>>>
>>> +case 9: /* ls: !C || Z -> !(C && !Z) */
>>> +cond = TCG_COND_NE;
>>> +value = tcg_temp_new_i32();
>>> +
Peter Maydell writes:
> On 7 September 2015 at 16:45, Markus Armbruster wrote:
>> A feature new in Python 2.7 crept into commit 77e703b: re.subn()'s
>> fifth argument. Avoid that, use re.compile().
>>
>> Reported-by: Laurent Desnogues
>> Signed-off-by: Markus Armbruster
>
> Should we cc: stab
On 08/09/2015 08:51, Salva Peiró wrote:
> Rigth, I should have started by providing the scenario where the fault occurs.
> The problem occurs performing a writeb to the BAR0 of device 1033:194.
> That is PCI_DEVICE_ID_NEC_UPD720200 0x0194 at hw/usb/hcd-xhci.c
>
> I've attached tests/nec-usb-xhc
On Wed, Sep 02, 2015 at 11:38:10AM -0700, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> This was originally posted back in February. I failed to keep
> any reply, if any, that may have been given. There's no change
> to the code after updating to mainline.
Thanks, I've mer
2015-09-08 11:00 GMT+03:00 Denis V. Lunev :
>
> VM remains stopped until all requests from the disk which caused VM's stopping
> are completed. Furthermore, if there is another disks with 'disk-deadlines=on'
> whose requests are waiting to be completed, do not start VM : wait completion
> of all "l
* Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote:
> On Tue, Sep 08, 2015 at 04:08:06PM +1000, Michael Ellerman wrote:
> > On Wed, 2015-08-12 at 10:53 +0530, Bharata B Rao wrote:
> > > On Tue, Aug 11, 2015 at 03:48:26PM +0200, Andrea Arcangeli wrote:
> > > > Hello Bharata,
> > > >
> > > > On Tue,
Some functions previously used only by vGICv2 are useful also for vGICv3
implementation. Untie them from GICState and make accessible from within
other modules:
- kvm_arm_gic_set_irq()
- kvm_gic_supports_attr() - moved to common code and renamed to
kvm_device_check_attr()
- kvm_gic_access() - tur
This series introduces support for GICv3 by KVM. Software emulation is
currently not supported.
v12 => v13:
- Many stylistic fixes
- Fixed up ACPI data for virt machine
- Added gic-version=host value which probes for best possible vGIC version
- Reserved regions for memory-mapped CPU/vCPU/HYP inte
Add gic_version to VirtMachineState, set it to value of the option
and pass it around where necessary. Instantiate devices and fdt
nodes according to the choice.
max_cpus for virt machine increased to 123 (calculated from redistributor
space available in the memory map). GICv2 compatibility check
This is the initial version of KVM-accelerated GICv3 support.
State load and save are not yet supported, live migration is
not possible.
In order to get correct class name in a simpler way, gicv3_class_name()
function is implemented, similar to gic_class_name().
Signed-off-by: Pavel Fedin
Review
From: Shlomo Pongratz
This class is to be used by both software and KVM implementations of GICv3
Currently it is mostly a placeholder, but in future it is supposed to hold
qemu's representation of GICv3 state, which is necessary for migration.
The interface of this class is fully compatible wit
This allows us to use different GIC types from v2. There are no kernels
which could advertise KVM_CAP_DEVICE_CTRL without the actual ability to
create GIC with it.
GIC version probe code moved to kvm_arm_vgic_probe() which will be used
later.
Signed-off-by: Pavel Fedin
Reviewed-by: Eric Auger
T
On 09/01/2015 11:30 PM, Eric Blake wrote:
> On 08/31/2015 06:44 PM, Wen Congyang wrote:
>
>>>
+ * Hot add/remove a BDS's child. So the user can take a child offline when
+ * it is broken and take a new child online
+ */
+void bdrv_add_child(BlockDriverState *bs, QDict *options,
On 07/21/2015 01:45 AM, Max Reitz wrote:
> And a helper function for that, which directly takes a pointer to the
> BDS to be inserted instead of its node-name (which will be used for
> implementing 'change' using blockdev-insert-medium).
>
> Signed-off-by: Max Reitz
> ---
> blockdev.c
[Cc'ing qemu-bl...@nongnu.org]
On Tue, 09/08 11:00, Denis V. Lunev wrote:
> To avoid such situation this patchset introduces patch per-drive option
> "disk-deadlines=on|off" which is unset by default.
The general idea sounds very nice. Thanks!
Should we allow user configuration on the timeout?
The oslib-win32 file currently provides a localtime_r and
gmtime_r replacement unconditionally. Some versions of
Mingw64 would provide crude macros for localtime_r/gmtime_r
which QEMU takes care to disable. Latest versions of Mingw64
now provide actual functions for localtime_r/gmtime_r, but
with a
When building for Mingw64 target on Fedora 22 a warning
is issued about _WIN32_WINNT being redefined.
In file included from ui/gtk.c:40:0:
include/ui/gtk.h:5:0: warning: "_WIN32_WINNT" redefined
# define _WIN32_WINNT 0x0601 /* needed to get definition of MAPVK_VK_TO_VSC */
^
In file included fr
On 08/09/2015 10:00, Denis V. Lunev wrote:
> How the given solution works?
>
> If disk-deadlines option is enabled for a drive, one controls time completion
> of this drive's requests. The method is as follows (further assume that this
> option is enabled).
>
> Every drive has its own red-black
On Tue, 09/08 11:00, Denis V. Lunev wrote:
> typedef struct DiskDeadlines {
> bool enabled;
> +bool expired_tree;
> +pthread_mutex_t mtx_tree;
This won't compile on win32, probably use QemuMutex instead?
In file included from /tmp/qemu-build/include/block/accounting.h:30:0,
On 08/09/2015 11:28, Daniel P. Berrange wrote:
> In file included from ui/gtk.c:40:0:
> include/ui/gtk.h:5:0: warning: "_WIN32_WINNT" redefined
> # define _WIN32_WINNT 0x0601 /* needed to get definition of MAPVK_VK_TO_VSC
> */
> ^
> In file included from
> /usr/i686-w64-mingw32/sys-root/ming
On 09/08/2015 12:33 PM, Paolo Bonzini wrote:
On 08/09/2015 10:00, Denis V. Lunev wrote:
How the given solution works?
If disk-deadlines option is enabled for a drive, one controls time completion
of this drive's requests. The method is as follows (further assume that this
option is enabled).
On 09/08/2015 12:35 PM, Fam Zheng wrote:
On Tue, 09/08 11:00, Denis V. Lunev wrote:
typedef struct DiskDeadlines {
bool enabled;
+bool expired_tree;
+pthread_mutex_t mtx_tree;
This won't compile on win32, probably use QemuMutex instead?
In file included from /tmp/qemu-build/inc
On 08/09/2015 11:41, Denis V. Lunev wrote:
> This solution is far not perfect as there is a race window for
> request complete anyway. Though the amount of failures is
> reduced by 2-3 orders of magnitude.
>
> The behavior is similar not for soft mounts, which could
> corrupt the data but to har
On 04/09/15 09:21, Alex Smith wrote:
> 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
On 08/09/2015 09:09, Denis V. Lunev wrote:
> qemu-monitor-info.texi | 151 +++
This should be added in patch 4, not now.
> +const MonitorDef *target_monitor_defs(void) __attribute__((weak));
> +
> +const MonitorDef *target_monitor_defs(void)
> +{
> +return NULL;
> +}
Weak sym
On 09/07/2015 05:21 PM, Peter Maydell wrote:
> CCing the net maintainers on this thread seems like it would
> be a good idea...
>
> On 7 September 2015 at 08:47, Richard Purdie
> wrote:
>> On Sun, 2015-09-06 at 17:48 -0700, Peter Crosthwaite wrote:
>>> This doesn't sound right. There are other n
On 02/09/2015 13:17, Daniel P. Berrange wrote:
> This small patch series is a formal submission of another part
> of my previous series
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg02038.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2015-08/msg01267.html
> v3: h
Am 08.09.2015 um 11:33 hat Paolo Bonzini geschrieben:
>
>
> On 08/09/2015 10:00, Denis V. Lunev wrote:
> > How the given solution works?
> >
> > If disk-deadlines option is enabled for a drive, one controls time
> > completion
> > of this drive's requests. The method is as follows (further assu
On 08/09/2015 10:44, Leon Alrae wrote:
> On 04/09/15 09:21, Alex Smith wrote:
>> 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.
>>
On 09/08/2015 01:07 PM, Kevin Wolf wrote:
Am 08.09.2015 um 11:33 hat Paolo Bonzini geschrieben:
On 08/09/2015 10:00, Denis V. Lunev wrote:
How the given solution works?
If disk-deadlines option is enabled for a drive, one controls time completion
of this drive's requests. The method is as fol
Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
> [Cc'ing qemu-bl...@nongnu.org]
>
> On Tue, 09/08 11:00, Denis V. Lunev wrote:
> > To avoid such situation this patchset introduces patch per-drive option
> > "disk-deadlines=on|off" which is unset by default.
>
> The general idea sounds very nic
On 09/08/2015 01:11 PM, Kevin Wolf wrote:
Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
[Cc'ing qemu-bl...@nongnu.org]
On Tue, 09/08 11:00, Denis V. Lunev wrote:
To avoid such situation this patchset introduces patch per-drive option
"disk-deadlines=on|off" which is unset by default.
The
On Tue, 09/08 11:54, Paolo Bonzini wrote:
>
>
> On 08/09/2015 09:09, Denis V. Lunev wrote:
> > qemu-monitor-info.texi | 151 +++
>
> This should be added in patch 4, not now.
>
> > +const MonitorDef *target_monitor_defs(void) __attribute__((weak));
> > +
> > +const MonitorDef *tar
ping
On Wed, Sep 2, 2015 at 1:09 PM, wrote:
> From: Marc-André Lureau
>
> QAPI_EVENT_VSERPORT_CHANGE reports changes of a virtio serial port
> state. However, the events may be for different ports, but the throttle
> mechanism may replace the event for a different port, since it only
> checks t
On Tue, Sep 08, 2015 at 11:35:15AM +0200, Paolo Bonzini wrote:
>
>
> On 08/09/2015 11:28, Daniel P. Berrange wrote:
> > In file included from ui/gtk.c:40:0:
> > include/ui/gtk.h:5:0: warning: "_WIN32_WINNT" redefined
> > # define _WIN32_WINNT 0x0601 /* needed to get definition of
> > MAPVK_VK_T
On Tue, 09/08 12:11, Kevin Wolf wrote:
> Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
> > [Cc'ing qemu-bl...@nongnu.org]
> >
> > On Tue, 09/08 11:00, Denis V. Lunev wrote:
> > > To avoid such situation this patchset introduces patch per-drive option
> > > "disk-deadlines=on|off" which is unse
On Tue, Sep 08, 2015 at 11:33:09AM +0200, Paolo Bonzini wrote:
>
>
> On 08/09/2015 10:00, Denis V. Lunev wrote:
> > How the given solution works?
> >
> > If disk-deadlines option is enabled for a drive, one controls time
> > completion
> > of this drive's requests. The method is as follows (fur
On Tue, Sep 08, 2015 at 09:59:47AM +0100, Dr. David Alan Gilbert wrote:
> * Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote:
> > In fact I had successfully done postcopy migration of sPAPR guest with
> > this setup.
>
> Interesting - I'd not got that far myself on power; I was hitting a problem
>
On 08/09/2015 12:22, Stefan Hajnoczi wrote:
> Guests running without this patch series may suffer from the NFS "soft"
> mounts problem when they time out and give up on the I/O request just as
> it actually completes on the server, leaving the data in a different
> state than expected.
>
> This
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
---
Changes in v2:
- Fix
When building for Mingw64 target on Fedora 22 a warning
is issued about _WIN32_WINNT being redefined.
In file included from ui/gtk.c:40:0:
include/ui/gtk.h:5:0: warning: "_WIN32_WINNT" redefined
# define _WIN32_WINNT 0x0601 /* needed to get definition of MAPVK_VK_TO_VSC */
^
In file included fr
On 09/08/2015 01:22 PM, Stefan Hajnoczi wrote:
On Tue, Sep 08, 2015 at 11:33:09AM +0200, Paolo Bonzini wrote:
On 08/09/2015 10:00, Denis V. Lunev wrote:
How the given solution works?
If disk-deadlines option is enabled for a drive, one controls time completion
of this drive's requests. The me
On Tue, Sep 8, 2015 at 12:41 PM, Denis V. Lunev wrote:
> On 09/08/2015 12:33 PM, Paolo Bonzini wrote:
>>
>>
>> On 08/09/2015 10:00, Denis V. Lunev wrote:
>>>
>>> How the given solution works?
>>>
>>> If disk-deadlines option is enabled for a drive, one controls time
>>> completion
>>> of this driv
On Tue, 2015-09-08 at 17:14 +1000, Michael Ellerman wrote:
> On Tue, 2015-09-08 at 12:09 +0530, Bharata B Rao wrote:
> > On Tue, Sep 08, 2015 at 04:08:06PM +1000, Michael Ellerman wrote:
> > > Hmm, not for me. See below.
> > >
> > > What setup were you testing on Bharata?
> >
> > I was on commit
On 09/08/2015 01:20 PM, Fam Zheng wrote:
On Tue, 09/08 12:11, Kevin Wolf wrote:
Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
[Cc'ing qemu-bl...@nongnu.org]
On Tue, 09/08 11:00, Denis V. Lunev wrote:
To avoid such situation this patchset introduces patch per-drive option
"disk-deadlines=o
Am 08.09.2015 um 12:20 hat Fam Zheng geschrieben:
> On Tue, 09/08 12:11, Kevin Wolf wrote:
> > Am 08.09.2015 um 11:20 hat Fam Zheng geschrieben:
> > > [Cc'ing qemu-bl...@nongnu.org]
> > >
> > > On Tue, 09/08 11:00, Denis V. Lunev wrote:
> > > > To avoid such situation this patchset introduces patc
On 09/08/2015 01:37 PM, Andrey Korolyov wrote:
On Tue, Sep 8, 2015 at 12:41 PM, Denis V. Lunev wrote:
On 09/08/2015 12:33 PM, Paolo Bonzini wrote:
On 08/09/2015 10:00, Denis V. Lunev wrote:
How the given solution works?
If disk-deadlines option is enabled for a drive, one controls time
comp
This patch doesn't apply on latest git commit i.e. 298fae389 from Sep 7.
Can you please rebase?
Best regards,
S.P.
Am 08.09.2015 um 10:00 hat Denis V. Lunev geschrieben:
> From: Raushaniya Maksudova
>
> If disk-deadlines option is enabled for a drive, one controls time
> completion of this drive's requests. The method is as follows (further
> assume that this option is enabled).
>
> Every drive has its own r
Paolo Bonzini writes:
> Coccinelle chokes on some idioms from compiler.h and queue.h.
> Extract those in a macro file, to be used with "--macro-file
> scripts/cocci-macro-file.h".
>
> Signed-off-by: Paolo Bonzini
I tested this as follows. Coccinelle can report on its parsing
difficulties:
$ s
Hi,
> I think the patches are great, and I'm not sure if anyone is in a better
> position than you to decide if they're ready.
Lets have a look:
# scripts/get_maintainer.pl -f crypto
"Daniel P. Berrange" (maintainer:Cryptography)
> I don't even know if anyone really understands the VNC TLS c
On 09/08/2015 02:06 PM, Kevin Wolf wrote:
Am 08.09.2015 um 10:00 hat Denis V. Lunev geschrieben:
From: Raushaniya Maksudova
If disk-deadlines option is enabled for a drive, one controls time
completion of this drive's requests. The method is as follows (further
assume that this option is enabl
On 08/09/15 11:34, Alex Smith wrote:
> 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
Marc-André Lureau writes:
> From: Marc-André Lureau
>
> Learn a few more markups used for API documentation.
>
> Signed-off-by: Marc-André Lureau
I believe texi2pod.pl was originally stolen, most likely from GCC. Have
you checked its current status there?
https://gcc.gnu.org/git/?p=gcc.git;a
On 8 September 2015 at 12:45, Markus Armbruster wrote:
> I believe texi2pod.pl was originally stolen, most likely from GCC. Have
> you checked its current status there?
>
> https://gcc.gnu.org/git/?p=gcc.git;a=history;f=contrib/texi2pod.pl;h=91bdbb5cea933d0381f2924ab94490fca31d5800;hb=HEAD
>
> Sh
On 09/07/2015 04:16 AM, Markus Armbruster wrote:
> One of the next patches will among other things generate a separate
> typedef for some struct types, i.e.
>
> typedef struct FOO FOO;
>
> struct FOO {
> ...
> };
>
> instead of
>
> typedef struct FOO {
> ...
> } FOO;
On 09/07/2015 04:16 AM, Markus Armbruster wrote:
> This reverts commit 6542034f356ebc6f2818c1c6b8c9a143f817bb2a.
Of course, this commit id doesn't match the one that is currently on
your qapi-introspect branch. But it doesn't matter, either :)
--
Eric Blake eblake redhat com+1-919-301-3266
* Michael Ellerman (m...@ellerman.id.au) wrote:
> On Tue, 2015-09-08 at 17:14 +1000, Michael Ellerman wrote:
> > On Tue, 2015-09-08 at 12:09 +0530, Bharata B Rao wrote:
> > > On Tue, Sep 08, 2015 at 04:08:06PM +1000, Michael Ellerman wrote:
> > > > Hmm, not for me. See below.
> > > >
> > > > What
> > +/* From qemu/compiler.h */
> > +#define QEMU_GNUC_PREREQ(maj, min) 1
> > +#define QEMU_NORETURN __attribute__ ((__noreturn__))
> > +#define QEMU_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
> > +#define QEMU_SENTINEL __attribute__((sentinel))
> > +#define QEMU_ARTIFICIAL __attribute_
* Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote:
> On Tue, Sep 08, 2015 at 09:59:47AM +0100, Dr. David Alan Gilbert wrote:
> > * Bharata B Rao (bhar...@linux.vnet.ibm.com) wrote:
> > > In fact I had successfully done postcopy migration of sPAPR guest with
> > > this setup.
> >
> > Interesting -
Peter Maydell writes:
> On 8 September 2015 at 12:45, Markus Armbruster wrote:
>> I believe texi2pod.pl was originally stolen, most likely from GCC. Have
>> you checked its current status there?
>>
>> https://gcc.gnu.org/git/?p=gcc.git;a=history;f=contrib/texi2pod.pl;h=91bdbb5cea933d0381f2924ab
ping ?
On 27/08/2015 21:33, Laurent Vivier wrote:
> Originally, timers were ticks based, and it made sense to
> add ticks to current time to know when to trigger an alarm.
>
> But since commit:
>
> 7447545 change all other clock references to use nanosecond resolution
> accessors
>
> All timer
ping ?
On 27/08/2015 21:33, Laurent Vivier wrote:
> Originally, timers were ticks based, and it made sense to
> add ticks to current time to know when to trigger an alarm.
>
> But since commit:
>
> 7447545 change all other clock references to use nanosecond resolution
> accessors
>
> All timer
ping ?
On 27/08/2015 21:33, Laurent Vivier wrote:
> Originally, timers were ticks based, and it made sense to
> add ticks to current time to know when to trigger an alarm.
>
> But since commit:
>
> 7447545 change all other clock references to use nanosecond resolution
> accessors
>
> All timer
ping ?
On 27/08/2015 21:33, Laurent Vivier wrote:
> hpet defines a clock period in femtoseconds but
> then converts it to nanoseconds to use the internal
> timers.
>
> We can define the period in nanoseconds and use it
> directly, this allows to remove muldiv64().
>
> We only need to convert the
On Tue, 8 Sep 2015 11:54:46 +0200
Paolo Bonzini wrote:
>
>
> On 08/09/2015 09:09, Denis V. Lunev wrote:
> > qemu-monitor-info.texi | 151 +++
>
> This should be added in patch 4, not now.
>
> > +const MonitorDef *target_monitor_defs(void) __attribute__((weak));
> > +
> > +const
On Tue, Sep 08, 2015 at 11:18:27AM +0800, Shannon Zhao wrote:
> On 2015/9/7 22:23, Leif Lindholm wrote:
> > The Debug Port Table 2 (DBG2) is mandated by the ARM Server Base Boot
> > Requirements specification. Add the DBG2 table definitions, and set up
> > an entry in the ARM virt machine for the p
> > This should be added in patch 4, not now.
> >
> > > +const MonitorDef *target_monitor_defs(void) __attribute__((weak));
> > > +
> > > +const MonitorDef *target_monitor_defs(void)
> > > +{
> > > +return NULL;
> > > +}
> >
> > Weak symbols do not work on all platforms. Luckily, making lib
Am 08.09.2015 um 13:27 hat Denis V. Lunev geschrieben:
> interesting point. Yes, it flushes all requests and most likely
> hangs inside waiting requests to complete. But fortunately
> this happens after the switch to paused state thus
> the guest becomes paused. That's why I have missed this
> fact
Eric Blake writes:
> On 09/07/2015 04:16 AM, Markus Armbruster wrote:
>> This reverts commit 6542034f356ebc6f2818c1c6b8c9a143f817bb2a.
>
> Of course, this commit id doesn't match the one that is currently on
> your qapi-introspect branch. But it doesn't matter, either :)
I forgot to fix them up,
Paolo Bonzini writes:
>> > +/* From qemu/compiler.h */
>> > +#define QEMU_GNUC_PREREQ(maj, min) 1
>> > +#define QEMU_NORETURN __attribute__ ((__noreturn__))
>> > +#define QEMU_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
>> > +#define QEMU_SENTINEL __attribute__((sentinel))
>> > +#defin
On Tue, Sep 08, 2015 at 11:27:08AM +0800, Shannon Zhao wrote:
>
>
> On 2015/9/7 22:23, Leif Lindholm wrote:
> > The DBG2 table can be considered a "companion" to SPCR - it points out
> > debug consoles available in the system.
> >
> > Signed-off-by: Leif Lindholm
> > ---
> > include/hw/acpi/ac
1 - 100 of 348 matches
Mail list logo
