;PARTSTAT=TENTATIVE;RSVP=TRU
E;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nelson...@windriver.com;X-NUM-GUESTS=0:mailto:nelson.ho@windriver.c
om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;RSVP=TRU
E;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nelson...@windriver.com;X-NUM-GUESTS=0:mailto:nelson.ho@windriver.c
om
X-MICROSOFT-CDO
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDA
这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。
这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。
;PARTSTAT=DECLINED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nelson...@windriver.com;X-NUM-GUESTS=0:mailto:nelson.ho@windriver.c
om
X-MICROSOFT-CDO-OWNERAPPTID:1454431283
CREATED
;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nelson...@windriver.com;X-NUM-GUESTS=0:mailto:nelson.ho@windriver.c
om
X-MICROSOFT-CDO
;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=nelson...@windriver.com;X-NUM-GUESTS=0:mailto:nelson.ho@windriver.c
om
X-MICROSOFT-CDO-OWNERAPPTID:871867794
CREATED
;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-569421550
CREATED:20230221T153950Z
DESCRIPTION:If you need call details\, please contact me: alex.ben...@linaro.org
LAST-MODIFIED:20241112T074603Z
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
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDA
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDA
;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-569421550
CREATED:20230221T153950Z
DESCRIPTION:If you need call details\, please contact me: alex.ben...@linaro.org
LAST-MODIFIED:20240807T134754Z
LOCATION:https
;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=LIU Zhiwei;X-NUM-GUESTS=0:mailto:zhiwei_...@linux.alibaba.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO
=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-1740392407
CREATED:20230221T153950Z
DESCRIPTION:If you need call details\, please contact me: alex.ben...@linaro.org
LAST-MODIFIED
;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=th...@redhat.com;X-NUM-GUESTS=0:mailto:th...@redhat.com
X-MICROSOFT-CDO-OWNERAPPTID:137834682
=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=LIU Zhiwei;X-NUM-GUESTS=0:mailto:zhiwei_...@linux.alibaba.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;RSVP=TRU
E;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID
=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;RSVP=TRU
E;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-1287337024
CREATED:20230221T153950Z
DESCRIPTION:If you need call details\, please contact me: alex.ben...@linaro.org
LAST-MODIFIED
;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=max.c...@sifive.com;X-NUM-GUESTS=0:mailto:max.c...@sifive.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT
=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=LIU Zhiwei;X-NUM-GUESTS=0:mailto:zhiwei_...@linux.alibaba.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDA
SVP=
TRUE;CN=z@139.com;X-NUM-GUESTS=0:mailto:z@139.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=LIU Zhiwei;X-NUM-GUESTS=0:mailto:zhiwei_...@linux.alibaba.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=
SVP=
TRUE;CN=z@139.com;X-NUM-GUESTS=0:mailto:z@139.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=LIU Zhiwei;X-NUM-GUESTS=0:mailto:zhiwei_...@linux.alibaba.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=
;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=max.c...@sifive.com;X-NUM-GUESTS=0:mailto:max.c...@sifive.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID
-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Chao Peng;X-NUM-GUESTS=0:mailto:chao.p.p...@linux.intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-1610811808
-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Chao Peng;X-NUM-GUESTS=0:mailto:chao.p.p...@linux.intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-1130186283
=NEEDS-ACTION;RSVP=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=mbur...@qti.qualcomm.com;X-NUM-GUESTS=0:mailto:mbur...@qti.qualcomm.com
X-MICROSOFT-CDO-OWNERAPPTID:-1326661108
CLASS:PUBLIC
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
s, pic, VIRT_SECURE_UART, secure_sysmem,
>> serial_hd(1));
>> }
>>
>> +vms->highmem_ecam &= vms->highmem && (!firmware_loaded || aarch64);
> Do you remember why this conditional is the way it is?
It comes from Laszlo's suggestion at
http://patchw
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
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 NUMA nodes and use them as the backend memory.
For
=
TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=mbur...@qti.qualcomm.com;X-NUM-GUESTS=0:mailto:mburton@qti.qualcomm
.com
X-MICROSOFT-CDO-OWNERAPPTID:-1326661108
CLASS:PUBLIC
CREATED
=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=mbur...@qti.qualcomm.com;X-NUM-GUESTS=0:mailto:mburton@qti.qualcomm
.com
X-MICROSOFT-CDO-OWNERAPPTID:-1610811808
CLASS:PUBLIC
CREATED
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
ttps://elixir.bootlin.com/linux/v6.5/source/include/linux/minmax.h
>
> I believe that's what Markus does in its own way :
>
>
> https://lore.kernel.org/qemu-devel/20230921121312.1301864-8-arm...@redhat.com/
I wasn't aware of the kernel's infrastructure. We can steal it if
people think it provides additional value. Make your case :)
ique local
variable name, as well as handling the const and non-const variants
with the one macro.
https://elixir.bootlin.com/linux/v6.5/source/include/linux/minmax.h
I believe that's what Markus does in its own way :
https://lore.kernel.org/qemu-devel/20230921121312.1301864-8-arm...@redhat.com/
Thanks,
C.
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
t) {
>>>> +return next;
>>>> +}
>>>> +
>>>> +next = calculate_time(t, MIN(t->match[0], t->match[1]));
>>>> +if (now < next) {
>>>> +return next;
>>>> +}
>>>> +
>>>> +next = calculate_time(t, 0);
>>>> +if (now < next) {
>>>> +return next;
>>>> +}
>>>> +
>>>> +/* We've missed all deadlines, fire interrupt and try again */
>>>> +timer_del(&t->timer);
>>>> +
>>>> +if (timer_overflow_interrupt(t)) {
>>>> +t->level = !t->level;
>>>> +qemu_set_irq(t->irq, t->level);
>>>>}
>>>>
>>>> -return next;
>>>> +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,
>>
>> The inner MAX() deals with the lack of ordering constraints between the
>> match values. I think the outer MAX() is redundant. We should probably
>> remove it. The match member is type uint32_t so it can't be negative. You
>> did steal that from an RFC patch :D
>
> I did ! Fixed there :
>
>
> https://patchwork.ozlabs.org/project/qemu-devel/patch/20230922155924.1172019-5-...@kaod.org/
>
Thanks. That one might be further down in my review queue 😅
Andrew
e
match member is type uint32_t so it can't be negative. You did steal that from
an RFC patch :D
I did ! Fixed there :
https://patchwork.ozlabs.org/project/qemu-devel/patch/20230922155924.1172019-5-...@kaod.org/
Cheers,
C.
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
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDA
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
-
unsubscribe qemu-devel@nongnu.org<mailto:qemu-devel@nongnu.org>
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=
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=1025 -global mch.extended-tseg-mbytes=128
-driv
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
It's been a while now, but i was always missing this feature in QEMU and
i'd love to see that patch land in QEMU one day.
I discovered that patch by searching for "start qemu with tabs visible"
and found this link:
https://patchwork.ozlabs.org/project/qemu-devel/patch/56d0
ways missing this feature in QEMU and i'd
love to see that patch land in QEMU one day.
I discovered that patch by searching for "start qemu with tabs visible" and
found this link:
https://patchwork.ozlabs.org/project/qemu-devel/patch/56d0203f.5060...@gmail.com/
Not sure why
'd love to see that patch land in QEMU one day.
I discovered that patch by searching for "start qemu with tabs visible"
and found this link:
https://patchwork.ozlabs.org/project/qemu-devel/patch/56d0203f.5060...@gmail.com/
Regards
- Felix
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
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 will also be reported via sense codes..." SCSI layer on
Solaris depends
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
1 - 100 of 394982 matches
Mail list logo
