On 20/2/25 11:07, Philippe Mathieu-Daudé wrote:
On 12/10/18 10:20, Daniel P. Berrangé wrote:
On Fri, Oct 12, 2018 at 02:22:06AM +0200, Philippe Mathieu-Daudé wrote:
Hi Paolo,
Here are the changes you suggested in
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02294.html
charde
On 12/10/18 10:20, Daniel P. Berrangé wrote:
On Fri, Oct 12, 2018 at 02:22:06AM +0200, Philippe Mathieu-Daudé wrote:
Hi Paolo,
Here are the changes you suggested in
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02294.html
chardev: Simplify IOWatchPoll::fd_can_read as a GSource
Hi Jintack,
I run into the same issue as you described in
https://lists.nongnu.org/archive/html/qemu-devel/2018-02/msg03876.html
I try to pass through MLNX VF and NVME to level2-vm, but both these two pci
device can display with lspci correctly, but have issue with driver.
My env are:
Host L
QAPI schema sanity review only.
"Ho-Ren (Jack) Chuang" writes:
> Introduce a new configuration option 'host-mem-type=' in the
> '-object memory-backend-ram', allowing users to specify
> from which type of memory to allocate.
>
> Users can specify 'cxlram' as an argument, and QEMU will then
> aut
On Tue, 9 Jan 2024 15:55:46 -0800
Hao Xiang wrote:
> On Tue, Jan 9, 2024 at 2:13 PM Gregory Price
> wrote:
> >
> > On Tue, Jan 09, 2024 at 01:27:28PM -0800, Hao Xiang wrote:
> > > On Tue, Jan 9, 2024 at 11:58 AM Gregory Price
> > > wrote:
> > > >
> > > > If you drop this line:
> > > >
> >
On Tue, Jan 9, 2024 at 2:13 PM Gregory Price wrote:
>
> On Tue, Jan 09, 2024 at 01:27:28PM -0800, Hao Xiang wrote:
> > On Tue, Jan 9, 2024 at 11:58 AM Gregory Price
> > wrote:
> > >
> > > If you drop this line:
> > >
> > > -numa node,memdev=vmem0,nodeid=1
> >
> > We tried this as well and it work
On Tue, Jan 09, 2024 at 01:27:28PM -0800, Hao Xiang wrote:
> On Tue, Jan 9, 2024 at 11:58 AM Gregory Price
> wrote:
> >
> > If you drop this line:
> >
> > -numa node,memdev=vmem0,nodeid=1
>
> We tried this as well and it works after going through the cxlcli
> process and created the devdax device
On Tue, Jan 9, 2024 at 11:58 AM Gregory Price
wrote:
>
> On Tue, Jan 09, 2024 at 11:33:04AM -0800, Hao Xiang wrote:
> > On Mon, Jan 8, 2024 at 5:13 PM Gregory Price
> > wrote:
> >
> > Sounds like the technical details are explained on the other thread.
> > From what I understand now, if we don't
On Tue, Jan 09, 2024 at 11:33:04AM -0800, Hao Xiang wrote:
> On Mon, Jan 8, 2024 at 5:13 PM Gregory Price
> wrote:
>
> Sounds like the technical details are explained on the other thread.
> From what I understand now, if we don't go through a complex CXL
> setup, it wouldn't go through the emula
On Mon, Jan 8, 2024 at 5:13 PM Gregory Price wrote:
>
> On Mon, Jan 08, 2024 at 05:05:38PM -0800, Hao Xiang wrote:
> > On Mon, Jan 8, 2024 at 2:47 PM Hao Xiang wrote:
> > >
> > > On Mon, Jan 8, 2024 at 9:15 AM Gregory Price
> > > wrote:
> > > >
> > > > On Fri, Jan 05, 2024 at 09:59:19PM -0800,
On Mon, Jan 08, 2024 at 05:05:38PM -0800, Hao Xiang wrote:
> On Mon, Jan 8, 2024 at 2:47 PM Hao Xiang wrote:
> >
> > On Mon, Jan 8, 2024 at 9:15 AM Gregory Price
> > wrote:
> > >
> > > On Fri, Jan 05, 2024 at 09:59:19PM -0800, Hao Xiang wrote:
> > > > On Wed, Jan 3, 2024 at 1:56 PM Gregory Price
On Mon, Jan 8, 2024 at 2:47 PM Hao Xiang wrote:
>
> On Mon, Jan 8, 2024 at 9:15 AM Gregory Price
> wrote:
> >
> > On Fri, Jan 05, 2024 at 09:59:19PM -0800, Hao Xiang wrote:
> > > On Wed, Jan 3, 2024 at 1:56 PM Gregory Price
> > > wrote:
> > > >
> > > > For a variety of performance reasons, thi
On Mon, Jan 8, 2024 at 9:15 AM Gregory Price wrote:
>
> On Fri, Jan 05, 2024 at 09:59:19PM -0800, Hao Xiang wrote:
> > On Wed, Jan 3, 2024 at 1:56 PM Gregory Price
> > wrote:
> > >
> > > For a variety of performance reasons, this will not work the way you
> > > want it to. You are essentially t
Hi Peter,
On 1/8/24 16:52, Peter Maydell wrote:
> On Fri, 22 Jun 2018 at 14:09, Peter Maydell wrote:
>> From: Eric Auger
>>
>> With this patch, virt-3.0 machine uses a new 256MB ECAM region
>> by default instead of the legacy 16MB one, if highmem is set
>> (LPAE supported by the guest) and (!fir
On Fri, Jan 05, 2024 at 09:59:19PM -0800, Hao Xiang wrote:
> On Wed, Jan 3, 2024 at 1:56 PM Gregory Price
> wrote:
> >
> > For a variety of performance reasons, this will not work the way you
> > want it to. You are essentially telling QEMU to map the vmem0 into a
> > virtual cxl device, and now
On Fri, 22 Jun 2018 at 14:09, Peter Maydell wrote:
>
> From: Eric Auger
>
> With this patch, virt-3.0 machine uses a new 256MB ECAM region
> by default instead of the legacy 16MB one, if highmem is set
> (LPAE supported by the guest) and (!firmware_loaded || aarch64).
>
> Indeed aarch32 mode FW m
On Wed, Jan 3, 2024 at 1:56 PM Gregory Price wrote:
>
> On Sun, Dec 31, 2023 at 11:53:15PM -0800, Ho-Ren (Jack) Chuang wrote:
> > Introduce a new configuration option 'host-mem-type=' in the
> > '-object memory-backend-ram', allowing users to specify
> > from which type of memory to allocate.
> >
On Tue, Jan 2, 2024 at 5:04 AM David Hildenbrand wrote:
>
> On 01.01.24 08:53, Ho-Ren (Jack) Chuang wrote:
> > Introduce a new configuration option 'host-mem-type=' in the
> > '-object memory-backend-ram', allowing users to specify
> > from which type of memory to allocate.
> >
> > Users can speci
On Sun, Dec 31, 2023 at 11:53:15PM -0800, Ho-Ren (Jack) Chuang wrote:
> Introduce a new configuration option 'host-mem-type=' in the
> '-object memory-backend-ram', allowing users to specify
> from which type of memory to allocate.
>
> Users can specify 'cxlram' as an argument, and QEMU will then
On 01.01.24 08:53, Ho-Ren (Jack) Chuang wrote:
Introduce a new configuration option 'host-mem-type=' in the
'-object memory-backend-ram', allowing users to specify
from which type of memory to allocate.
Users can specify 'cxlram' as an argument, and QEMU will then
automatically locate CXL RAM NU
Hi Jack,
On 1/1/24 08:53, Ho-Ren (Jack) Chuang wrote:
Introduce a new configuration option 'host-mem-type=' in the
'-object memory-backend-ram', allowing users to specify
from which type of memory to allocate.
Users can specify 'cxlram' as an argument, and QEMU will then
automatically locate CX
On 21/08/23 5:31 pm, manish.mishra wrote:
Hi Everyone,
We are facing this issue. I see this conversation was never conversed and discussed issue
is still active on QEMU master. Just for summary, the solution mentioned in this thread
"temporarily enable bus master memory region" was not taken
Cédric Le Goater writes:
> On 9/27/23 04:12, Joel Stanley wrote:
>> On Fri, 22 Sept 2023 at 13:21, Cédric Le Goater wrote:
>>
+t->start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+return calculate_time(t, MAX(MAX(t->match[0], t->match[1]), 0));
>>>
>>> This MAX(MAX(x, y), 0) loo
On 9/27/23 04:12, Joel Stanley wrote:
On Fri, 22 Sept 2023 at 13:21, Cédric Le Goater wrote:
+t->start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+return calculate_time(t, MAX(MAX(t->match[0], t->match[1]), 0));
This MAX(MAX(x, y), 0) looks strange to me. Would you remember where it co
On Fri, 22 Sept 2023 at 13:21, Cédric Le Goater wrote:
> > +t->start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
> > +return calculate_time(t, MAX(MAX(t->match[0], t->match[1]), 0));
>
> This MAX(MAX(x, y), 0) looks strange to me. Would you remember where it comes
> from ? Thanks,
That look
On Mon, 25 Sep 2023, at 18:50, Cédric Le Goater wrote:
> On 9/25/23 09:54, Andrew Jeffery wrote:
>>
>>
>> On Fri, 22 Sep 2023, at 22:51, Cédric Le Goater wrote:
>>> Joel, Andrew,
>>>
>>> On 5/25/19 17:12, Cédric Le Goater wrote:
From: Joel Stanley
The Linux kernel driver was up
On 9/25/23 09:54, Andrew Jeffery wrote:
On Fri, 22 Sep 2023, at 22:51, Cédric Le Goater wrote:
Joel, Andrew,
On 5/25/19 17:12, Cédric Le Goater wrote:
From: Joel Stanley
The Linux kernel driver was updated in commit 4451d3f59f2a
("clocksource/drivers/fttmr010: Fix set_next_event handler) t
On Fri, 22 Sep 2023, at 22:51, Cédric Le Goater wrote:
> Joel, Andrew,
>
> On 5/25/19 17:12, Cédric Le Goater wrote:
>> From: Joel Stanley
>>
>> The Linux kernel driver was updated in commit 4451d3f59f2a
>> ("clocksource/drivers/fttmr010: Fix set_next_event handler) to fix an
>> issue observed
Joel, Andrew,
On 5/25/19 17:12, Cédric Le Goater wrote:
From: Joel Stanley
The Linux kernel driver was updated in commit 4451d3f59f2a
("clocksource/drivers/fttmr010: Fix set_next_event handler) to fix an
issue observed on hardware:
> RELOAD register is loaded into COUNT register when the as
On Tue, Sep 10, 2019 at 10:08:20AM -0400, John Snow wrote:
>
>
> On 9/10/19 9:58 AM, Michael S. Tsirkin wrote:
> > On Tue, Sep 10, 2019 at 09:50:41AM -0400, John Snow wrote:
> >>
> >>
> >> On 9/10/19 3:04 AM, Michael S. Tsirkin wrote:
> >>> On Tue, Sep 10, 2019 at 01:18:37AM +0800, andychiu wrote
On Tue, 1 Aug 2023 13:00:02 -0400
"Annie.li" wrote:
> Hi Igor,
>
> On 7/14/2023 10:04 AM, Igor Mammedov wrote:
> > On Fri, 7 Jul 2023 13:43:36 -0400
> > "Annie.li" wrote:
> >
> >> Hi Igor,
> >>
> >> Revisiting this thread and have more questions, please clarify, thank you!
> >>
> >> On 9/20/2
Hi Everyone,
We are facing this issue. I see this conversation was never conversed and discussed issue
is still active on QEMU master. Just for summary, the solution mentioned in this thread
"temporarily enable bus master memory region" was not taken with the following
justification.
"Poking
Hi Igor,
On 7/14/2023 10:04 AM, Igor Mammedov wrote:
On Fri, 7 Jul 2023 13:43:36 -0400
"Annie.li" wrote:
Hi Igor,
Revisiting this thread and have more questions, please clarify, thank you!
On 9/20/2021 3:53 AM, Igor Mammedov wrote:
On Fri, 6 Aug 2021 16:18:09 -0400
"Annie.li" wrote:
H
On Fri, 7 Jul 2023 13:43:36 -0400
"Annie.li" wrote:
> Hi Igor,
>
> Revisiting this thread and have more questions, please clarify, thank you!
>
> On 9/20/2021 3:53 AM, Igor Mammedov wrote:
> > On Fri, 6 Aug 2021 16:18:09 -0400
> > "Annie.li" wrote:
> >
> >> Hello Igor,
> >>
> >> This is an o
Hi Igor,
Revisiting this thread and have more questions, please clarify, thank you!
On 9/20/2021 3:53 AM, Igor Mammedov wrote:
On Fri, 6 Aug 2021 16:18:09 -0400
"Annie.li" wrote:
Hello Igor,
This is an old patch, but it does what we need.
I am getting a little bit lost about not implementin
On Mon, 19 Feb 2018 at 11:44, Marcel Apfelbaum wrote:
>
> From: Yuval Shaia
>
> First PVRDMA sub-module - implementation of the PVRDMA device.
> - PVRDMA commands such as create CQ and create MR.
> - Data path QP operations - post_send and post_recv.
> - Completion handler.
>
> Reviewed-by: Dotan
On 3/6/23 06:11, Philippe Mathieu-Daudé wrote:
Hi Palmer, Bastian,
(old patch)
On 12/3/19 14:15, Palmer Dabbelt wrote:
From: Bastian Koppelmann
Acked-by: Alistair Francis
Reviewed-by: Richard Henderson
Signed-off-by: Bastian Koppelmann
Signed-off-by: Peer Adelt
Signed-off-by: Palmer Dabb
Hi Palmer, Bastian,
(old patch)
On 12/3/19 14:15, Palmer Dabbelt wrote:
From: Bastian Koppelmann
Acked-by: Alistair Francis
Reviewed-by: Richard Henderson
Signed-off-by: Bastian Koppelmann
Signed-off-by: Peer Adelt
Signed-off-by: Palmer Dabbelt
---
target/riscv/insn32.decode
On 16/2/23 15:23, Marc-André Lureau wrote:
Hi Philippe
On Thu, Feb 16, 2023 at 2:14 AM Philippe Mathieu-Daudé
wrote:
Hi Marc-André,
[very old patch...]
On 22/10/16 11:52, Marc-André Lureau wrote:
In most cases, front ends do not care about the side effect of
CharBackend, so we can simply s
Hi Philippe
On Thu, Feb 16, 2023 at 2:14 AM Philippe Mathieu-Daudé
wrote:
>
> Hi Marc-André,
>
> [very old patch...]
>
> On 22/10/16 11:52, Marc-André Lureau wrote:
> > In most cases, front ends do not care about the side effect of
> > CharBackend, so we can simply skip the checks and call the qe
Hi Marc-André,
[very old patch...]
On 22/10/16 11:52, Marc-André Lureau wrote:
In most cases, front ends do not care about the side effect of
CharBackend, so we can simply skip the checks and call the qemu_chr_fe
functions even without associated CharDriver.
Signed-off-by: Marc-André Lureau
-
On Wed, 2017-06-21 at 13:45 -0700, Anatol Pomozov wrote:
> Hi Adam, thank you for your reply.
>
> On Mon, Jun 19, 2017 at 2:08 PM, Adam Lackorzynski
> wrote:
> > Hi,
> >
> > On Tue Jun 13, 2017 at 17:05:41 -0700, Anatol Pomozov wrote:
> > > Do these arguments sound reasonable to apply the patch?
Hi Thomas,
Thank you for the suggestion about the next step.
Do you know if there is an option to change this parameter in the runtime?
While looking for answer I found this presentation from 2008 which makes me
think that this may not
be the only limit:
https://www.linux-kvm.org/images/b/be/KvmFo
On 14/11/2022 23.58, Pawel Polawski wrote:
Hi Everyone,
I am trying to check qemu virtual cpu boundaries when running a custom
edk2 based firmware build. For that purpose I want to run qemu with more
than 1024 vCPU:
$QEMU
-accel kvm
-m 4G
-M q35,kernel-irqchip=on,smm=on
-smp cpus=1025,maxcpus=
On Thu, Sep 01, 2022 at 12:55:36PM +0100, Alex Bennée wrote:
>
> "Wang, Lei" writes:
>
> > On 9/1/2022 4:12 PM, Daniel P. Berrangé wrote:
> >> On Thu, Sep 01, 2022 at 09:08:33AM +0800, Wang, Lei wrote:
> >>> On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
> On Wed, Aug 31, 2022 at 05:18:34P
On 9/1/2022 7:55 PM, Alex Bennée wrote:
>
> "Wang, Lei" writes:
>
>> On 9/1/2022 4:12 PM, Daniel P. Berrangé wrote:
>>> On Thu, Sep 01, 2022 at 09:08:33AM +0800, Wang, Lei wrote:
On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
> On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
"Wang, Lei" writes:
> On 9/1/2022 4:12 PM, Daniel P. Berrangé wrote:
>> On Thu, Sep 01, 2022 at 09:08:33AM +0800, Wang, Lei wrote:
>>> On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
>
>
> On 8/31/2022 4:49 PM, Daniel P
On 9/1/2022 4:12 PM, Daniel P. Berrangé wrote:
> On Thu, Sep 01, 2022 at 09:08:33AM +0800, Wang, Lei wrote:
>> On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
>>> On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
On 8/31/2022 4:49 PM, Daniel P. Berrangé wrote:
> On Wed,
On Thu, Sep 01, 2022 at 09:08:33AM +0800, Wang, Lei wrote:
> On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
> > On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
> > >
> > >
> > > On 8/31/2022 4:49 PM, Daniel P. Berrangé wrote:
> > > > On Wed, Aug 31, 2022 at 02:23:51PM +0800, Wang, Lei
On 8/31/2022 6:39 PM, Daniel P. Berrangé wrote:
On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
On 8/31/2022 4:49 PM, Daniel P. Berrangé wrote:
On Wed, Aug 31, 2022 at 02:23:51PM +0800, Wang, Lei wrote:
On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
From: Marc-André Lu
On Wed, Aug 31, 2022 at 05:18:34PM +0800, Wang, Lei wrote:
>
>
> On 8/31/2022 4:49 PM, Daniel P. Berrangé wrote:
> > On Wed, Aug 31, 2022 at 02:23:51PM +0800, Wang, Lei wrote:
> > >
> > > On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
> > > > From: Marc-André Lureau
> > > >
> > > > c
Hi
On Wed, Aug 31, 2022 at 10:24 AM Wang, Lei wrote:
>
> On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > clang-format is awesome to reflow your code according to qemu coding
> > style in an editor (in the region you modify).
> >
> > (note: clang-tidy
On 8/31/2022 4:49 PM, Daniel P. Berrangé wrote:
On Wed, Aug 31, 2022 at 02:23:51PM +0800, Wang, Lei wrote:
On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
clang-format is awesome to reflow your code according to qemu coding
style in an editor (in the regio
On Wed, Aug 31, 2022 at 02:23:51PM +0800, Wang, Lei wrote:
>
> On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > clang-format is awesome to reflow your code according to qemu coding
> > style in an editor (in the region you modify).
> >
> > (note: clan
On 10/2/2015 1:30 AM, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
clang-format is awesome to reflow your code according to qemu coding
style in an editor (in the region you modify).
(note: clang-tidy should be able to add missing braces around
statements, but I haven't tried i
On Tue, 20 Aug 2019 at 08:12, Paolo Bonzini wrote:
>
> There is a race between TCG and accesses to the dirty log:
>
> vCPU thread reader thread
> --- ---
> TLB check -> slow path
> notdirty_mem_write
>
Ping?
On 2022-05-31 15:22:37 -0500, Venu Busireddy wrote:
> When a disk is hotplugged, QEMU reports a VIRTIO_SCSI_EVT_RESET_RESCAN
> event, but does not send the "REPORTED LUNS CHANGED" sense data. This
> does not conform to Section 5.6.6.3 of the VirtIO specification, which
> states "Events wil
On Thu, 31 Jan 2019 at 21:10, Richard Henderson
wrote:
>
> Assuming that the ISA clearly describes how to determine
> the length of the instruction, and the ISA has a reasonable
> maximum instruction length, the input to the decoder can be
> right-justified in an appropriate insn word.
>
> This is
On 23/06/2022 17.05, Felix Queißner wrote:
Not sure why it was never picked up
That patch certainly needs a re-spin since it won't apply as-is anymore.
Want to have a try?
I guess the semantics of the code stay the same, but the boilerplate might
change a bit?
If so, i guess i can give i
Not sure why it was never picked up
That patch certainly needs a re-spin since it won't apply as-is anymore.
Want to have a try?
I guess the semantics of the code stay the same, but the boilerplate
might change a bit?
If so, i guess i can give it a try tomorrow and see if i can make it w
On 23/06/2022 16.59, Thomas Huth wrote:
On 23/06/2022 16.36, Felix Queißner wrote:
Heya!
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be
enabled by hand at each start of the VM.
It's been a while now
On 23/06/2022 16.36, Felix Queißner wrote:
Heya!
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be
enabled by hand at each start of the VM.
It's been a while now, but i was always missing this feature i
Heya!
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be enabled by hand at
each start of the VM.
It's been a while now, but i was always missing this feature in QEMU and
i'd love to see that patch land
Ping?
On 2022-05-31 15:22:37 -0500, Venu Busireddy wrote:
> When a disk is hotplugged, QEMU reports a VIRTIO_SCSI_EVT_RESET_RESCAN
> event, but does not send the "REPORTED LUNS CHANGED" sense data. This
> does not conform to Section 5.6.6.3 of the VirtIO specification, which
> states "Events wil
On Thu, Apr 28, 2022 at 01:16:51PM +0200, Jason A. Donenfeld wrote:
> Hey again,
>
> On Thu, Apr 28, 2022 at 02:04:29AM +0200, Jason A. Donenfeld wrote:
> > By the way, would this also help the reboot case? That's
> > `reboot(RB_AUTOBOOT);`, which does:
> >
> > machine_restart() ->
> > do_kerne
Hey again,
On Thu, Apr 28, 2022 at 02:04:29AM +0200, Jason A. Donenfeld wrote:
> By the way, would this also help the reboot case? That's
> `reboot(RB_AUTOBOOT);`, which does:
>
> machine_restart() ->
> do_kernel_restart() ->
> atomic_notifier_chain_register(&restart_handler_list, nb) ->
>
On Wed, 27 Apr 2022 at 23:27, Stafford Horne wrote:
> Yes, this is what was brought up before. At that time semihosting was
> mentioned
> and I tried to understand what it was but didn't really understand it as a
> general
> concept. Is this something arm specific?
QEMU uses "semihosting" for
Hi Stafford,
On Thu, Apr 28, 2022 at 06:48:27AM +0900, Stafford Horne wrote:
> On Wed, Apr 27, 2022 at 07:47:33PM +0100, Peter Maydell wrote:
> > On Wed, 27 Apr 2022 at 18:46, Jason A. Donenfeld wrote:
> > >
> > > Hey Stafford,
> > >
> > > On Mon, Apr 17, 2017 at 08:23:51AM +0900, Stafford Horne
On Wed, Apr 27, 2022 at 07:47:33PM +0100, Peter Maydell wrote:
> On Wed, 27 Apr 2022 at 18:46, Jason A. Donenfeld wrote:
> >
> > Hey Stafford,
> >
> > On Mon, Apr 17, 2017 at 08:23:51AM +0900, Stafford Horne wrote:
> > > In openrisc simulators we use hooks like 'l.nop 1' to cause the
> > > simulat
On Wed, 27 Apr 2022 at 18:46, Jason A. Donenfeld wrote:
>
> Hey Stafford,
>
> On Mon, Apr 17, 2017 at 08:23:51AM +0900, Stafford Horne wrote:
> > In openrisc simulators we use hooks like 'l.nop 1' to cause the
> > simulator to exit. Implement that for qemu too.
> >
> > Reported-by: Waldemar Brodk
Hey Stafford,
On Mon, Apr 17, 2017 at 08:23:51AM +0900, Stafford Horne wrote:
> In openrisc simulators we use hooks like 'l.nop 1' to cause the
> simulator to exit. Implement that for qemu too.
>
> Reported-by: Waldemar Brodkorb
> Signed-off-by: Stafford Horne
I'm curious as to why this never
On 12/04/22 8:46 pm, Vitaly Kuznetsov wrote:
Divya Garg writes:
On 12/04/22 6:18 pm, Vitaly Kuznetsov wrote:
Divya Garg writes:
Hi Vitaly Kuznetsov !
I was working on hyperv flags and saw that we introduced new
dependencies some
time back
(https://urldefense.proofpoint.com/v2/url?u=https
Divya Garg writes:
> On 12/04/22 6:18 pm, Vitaly Kuznetsov wrote:
>> Divya Garg writes:
>>
>>> Hi Vitaly Kuznetsov !
>>> I was working on hyperv flags and saw that we introduced new
>>> dependencies some
>>> time back
>>> (https://urldefense.proofpoint.com/v2/url?u=https-3A__sourcegraph.com_gith
On 12/04/22 6:18 pm, Vitaly Kuznetsov wrote:
Divya Garg writes:
Hi Vitaly Kuznetsov !
I was working on hyperv flags and saw that we introduced new
dependencies some
time back
(https://urldefense.proofpoint.com/v2/url?u=https-3A__sourcegraph.com_github.com_qemu_qemu_-2D_commit_c686193072a4703
Divya Garg writes:
> Hi Vitaly Kuznetsov !
> I was working on hyperv flags and saw that we introduced new
> dependencies some
> time back
> (https://sourcegraph.com/github.com/qemu/qemu/-/commit/c686193072a47032d83cb4e131dc49ae30f9e5d7?visible=1).
> After these changes, if we try to live migrat
On Thu, 7 Apr 2022 at 12:28, Frederic Konrad wrote:
> So I'm not totally sure.. do you need a patch for 7.0.0?
It's not a regression, so we can fix this for 7.1.
thanks
-- PMM
Le 4/7/22 à 12:32, Peter Maydell a écrit :
On Tue, 14 Jun 2016 at 15:40, Peter Maydell wrote:
From: KONRAD Frederic
This is the implementation of the DisplayPort.
It has an aux-bus to access dpcd and edid.
Graphic plane is connected to the channel 3.
Video plane is connected to the chann
On Tue, 14 Jun 2016 at 15:40, Peter Maydell wrote:
>
> From: KONRAD Frederic
>
> This is the implementation of the DisplayPort.
> It has an aux-bus to access dpcd and edid.
>
> Graphic plane is connected to the channel 3.
> Video plane is connected to the channel 0.
> Audio stream are connected t
On Thu, Mar 31, 2022 at 11:03:49AM +0100, Peter Maydell wrote:
> On Mon, 29 Jan 2018 at 10:24, Gerd Hoffmann wrote:
> >
> > From: "Daniel P. Berrange"
> >
> > Replace the qcode_to_keycode table with automatically
> > generated tables.
> >
> > Missing entries in qcode_to_keycode now fixed:
> >
> >
On Mon, 29 Jan 2018 at 10:24, Gerd Hoffmann wrote:
>
> From: "Daniel P. Berrange"
>
> Replace the qcode_to_keycode table with automatically
> generated tables.
>
> Missing entries in qcode_to_keycode now fixed:
>
> - Q_KEY_CODE_KP_COMMA -> 0x2d
>
> Signed-off-by: Daniel P. Berrange
> Message-id
On Thu, Jan 27, 2022 at 2:10 PM Peter Maydell
wrote:
> On Fri, 2 Nov 2018 at 17:24, Peter Maydell
> wrote:
> >
> > From: "Edgar E. Iglesias"
> >
> > Add a virtual Xilinx Versal board.
> >
> > This board is based on the Xilinx Versal SoC. The exact
> > details of what peripherals are attached to
On Fri, 15 Feb 2019 at 16:06, Daniel P. Berrangé wrote:
>
> The inotify userspace API for reading events is quite horrible, so it is
> useful to wrap it in a more friendly API to avoid duplicating code
> across many users in QEMU. Wrapping it also allows introduction of a
> platform portability la
On Fri, Jan 28, 2022 at 04:17:32PM +, Peter Maydell wrote:
> On Fri, 15 Feb 2019 at 16:06, Daniel P. Berrangé wrote:
> >
> > The inotify userspace API for reading events is quite horrible, so it is
> > useful to wrap it in a more friendly API to avoid duplicating code
> > across many users in
On Fri, 2 Nov 2018 at 17:24, Peter Maydell wrote:
>
> From: "Edgar E. Iglesias"
>
> Add a virtual Xilinx Versal board.
>
> This board is based on the Xilinx Versal SoC. The exact
> details of what peripherals are attached to this board
> will remain in control of QEMU. QEMU will generate an
> FDT
On Fri, Jan 07, 2022 at 12:06:47PM +, Daniel P. Berrangé wrote:
> On Fri, Jan 07, 2022 at 12:55:42PM +0100, Thomas Huth wrote:
> > On 07/01/2022 12.43, Andrea Bolognani wrote:
> > > On Thu, Aug 29, 2019 at 10:15:05AM +0100, Daniel P. Berrangé wrote:
> > > > Where are you seeing pkg-config files
On Fri, Jan 07, 2022 at 12:55:42PM +0100, Thomas Huth wrote:
> On 07/01/2022 12.43, Andrea Bolognani wrote:
> > On Thu, Aug 29, 2019 at 10:15:05AM +0100, Daniel P. Berrangé wrote:
> > > On Thu, Aug 29, 2019 at 04:53:02PM +0800, zhe...@windriver.com wrote:
> > > > libgcrypt may also be controlled by
On 07/01/2022 12.43, Andrea Bolognani wrote:
On Thu, Aug 29, 2019 at 10:15:05AM +0100, Daniel P. Berrangé wrote:
On Thu, Aug 29, 2019 at 04:53:02PM +0800, zhe...@windriver.com wrote:
libgcrypt may also be controlled by pkg-config, this patch adds pkg-config
handling for libgcrypt.
Where are y
On Thu, Aug 29, 2019 at 10:15:05AM +0100, Daniel P. Berrangé wrote:
> On Thu, Aug 29, 2019 at 04:53:02PM +0800, zhe...@windriver.com wrote:
> > libgcrypt may also be controlled by pkg-config, this patch adds pkg-config
> > handling for libgcrypt.
>
> Where are you seeing pkg-config files for libgcr
On 4/25/19 22:00, Eduardo Habkost wrote:
> Now that qdev_get_machine_hotplug_handler() is only compiled in
> softmmu mode, we don't need to check if qdev_gt_machine() is
> really of type TYPE_MACHINE.
>
> Signed-off-by: Eduardo Habkost
> ---
> hw/core/qdev-hotplug.c | 13 -
> 1 file
On 4/25/19 22:00, Eduardo Habkost wrote:
> Eduardo Habkost (4):
> machine: Move gpio code to hw/core/gpio.c
> move qdev hotplug code to qdev-hotplug.c
> qdev: Don't compile hotplug code in user-mode emulation
> qdev-hotplug: Don't check type of qdev_get_machine()
Patch 1 queued to machine
On 4/25/19 22:00, Eduardo Habkost wrote:
> Only softmmu code uses gpio, so move gpio code from qdev.c to
> gpio.c and compile it only on softmmu mode.
>
> Signed-off-by: Eduardo Habkost
> ---
> hw/core/gpio.c| 206 ++
> hw/core/qdev.c| 184
Peter Maydell writes:
> On Fri, 24 Sept 2021 at 15:43, Daniel P. Berrangé wrote:
>>
>> On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
>> > Peter Maydell writes:
>> > > Side side note: the JSON event doesn't seem to contemplate
>> > > the possibility that a machine might have
On Fri, 24 Sept 2021 at 15:43, Daniel P. Berrangé wrote:
>
> On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
> > Peter Maydell writes:
> > > Side side note: the JSON event doesn't seem to contemplate
> > > the possibility that a machine might have more than one RTC...
> >
> > R
On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
> >> ... this isn't really *target*-specific, it's *device*-specific: some
> >> devices implement the event, some don't.
> >>
> >> Ideally, we'
Peter Maydell writes:
> On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
>> ... this isn't really *target*-specific, it's *device*-specific: some
>> devices implement the event, some don't.
>>
>> Ideally, we'd just fix that.
>
> Would you want to tell the far end "this machine simply does
On Fri, 24 Sept 2021 at 13:29, Marc-André Lureau
wrote:
> On Fri, Sep 24, 2021 at 4:21 PM Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>> > Could we reconsider this change? It seems to me to be adding
>> > complexity and build time and I don't really see the advantage
>> > that compensat
On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
> ... this isn't really *target*-specific, it's *device*-specific: some
> devices implement the event, some don't.
>
> Ideally, we'd just fix that.
Would you want to tell the far end "this machine simply does
not have an RTC device at all (b
Hi
On Fri, Sep 24, 2021 at 4:21 PM Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On Mon, 18 Feb 2019 at 14:19, Markus Armbruster
> wrote:
> >>
> >> From: Marc-André Lureau
> >>
> >> A few targets don't emit RTC_CHANGE, we could restrict the event to
> >> the tagets that do emit it.
>
Peter Maydell writes:
> On Mon, 18 Feb 2019 at 14:19, Markus Armbruster wrote:
>>
>> From: Marc-André Lureau
>>
>> A few targets don't emit RTC_CHANGE, we could restrict the event to
>> the tagets that do emit it.
>>
>> Note: There is a lot more of events & commands that we could restrict
>> to
1 - 100 of 337353 matches
Mail list logo
