- Linaro-open-discussions - op-lists.linaro.org

Fwd: LPM and Linaro Connect London April 24-28 2023

by Joyce Qi

Hi NanJonathanKangkang Welcome Huawei to join Linaro Connect London and LPM meeting on April 24-28 2023. As our core membership, Huawei has 5 free tickets,and you can book the hotel now. @Nan, will I share the free register code to you? Thanks:) Joyce : Andrea Gallo <[1]andrea.gallo(a)linaro.org> : LPM and Linaro Connect London April 24-28 2023 : 20221216 GMT+8 5:07:28 : Andrew Wafaa <[2]andrew.wafaa(a)arm.com>, Andy Harker <[3]andy.harker(a)arm.com>, Anmar Oueja <[4]anmar.oueja(a)linaro.org>, Azzedine Touzni Qualcomm <[5]atouzni(a)qti.qualcomm.com>, Bill Fletcher <[6]bill.fletcher(a)linaro.org>, "Northway, Craig" <[7]craign(a)qti.qualcomm.com>, Daniel Thompson <[8]daniel.thompson(a)linaro.org>, Davide Ricci <[9]davide.ricci(a)huawei.com>, Don Harbin <[10]don.harbin(a)linaro.org>, Ebba Simpson <[11]ebba.simpson(a)linaro.org>, Eric Finco <[12]eric.finco(a)st.com>, Fang liu <[13]fang.liu(a)cixcomputing.com>, Gen Shimada <[14]gen.shimada(a)linaro.org>, Grant Likely <[15]grant.likely(a)linaro.org>, Hansheng Tan <[16]hans.tan(a)zeku.com>, James King <[17]james.king(a)arm.com>, "Jammy.Zhou" <[18]jammy.zhou(a)cixcomputing.com>, [19]jason.martin1(a)nxp.com, Jered Floyd <[20]jered(a)redhat.com>, Joakim Bech <[21]joakim.bech(a)linaro.org>, Joe Bates <[22]joe.bates(a)linaro.org>, Jonathan Cameron <[23]jonathan.cameron(a)huawei.com>, Jon Masters <[24]jonmasters(a)google.com>, Joyce Qi <[25]joyce.qi(a)linaro.org>, Kangkang Shen <[26]kangkang.shen(a)futurewei.com>, Kangkang Shen <[27]kshen(a)futurewei.com>, Leendert van Doorn <[28]leendert(a)qti.qualcomm.com>, Leonardo Garcia <[29]leonardo.garcia(a)linaro.org>, Li Gong <[30]li.gong(a)linaro.org>, Loic Pallardy <[31]loic.pallardy(a)st.com>, Larry Wikelius <[32]lwikeliu(a)qti.qualcomm.com>, Marcus Perryman <[33]marcus.perryman(a)microsoft.com>, Mark Hambleton <[34]mark.hambleton(a)arm.com>, "Wangke (Michael Wang)" <[35]michael.wangke(a)huawei.com>, Mike Holmes <[36]mike.holmes(a)linaro.org>, Nicolas Dechesne <[37]nicolas.dechesne(a)linaro.org>, Kiyoshi Owada <[38]owada.kiyoshi(a)socionext.com>, Peter Robinson <[39]pbrobinson(a)redhat.com>, [40]rajav(a)quicinc.com, Rami Husseini <[41]ramih(a)qti.qualcomm.com>, Randy Linnell <[42]randy.linnell(a)linaro.org>, Rob Booth <[43]rob.booth(a)linaro.org>, Rob Oshana <[44]robert.oshana(a)nxp.com>, Ryan Arnold <[45]ryan.arnold(a)linaro.org>, [46]ryu.real(a)samsung.com, Scott Bambrough <[47]scott.bambrough(a)linaro.org>, Sean Rogers <[48]seanr(a)quicinc.com>, Satish Sellaiah <[49]sellaiah(a)google.com>, Sandeep Singhai <[50]ssinghai(a)quicinc.com>, Tim Benton <[51]tim.benton(a)linaro.org>, Todd Kjos <[52]tkjos(a)google.com>, Tom Gall <[53]tom.gall(a)linaro.org>, Tomas Evensen <[54]tomase(a)xilinx.com>, Trilok Soni <[55]tsoni(a)quicinc.com>, Yang Zhang <[56]yang.zhang(a)96boards.org>, [57]k-hirai(a)fujitsu.com Dear members, The next Linaro Connect will be held in London, United Kingdom, from Wednesday 26 till Friday 28 April 2023 at the Park Plaza Riverbank. [58]https://www.linaro.org/connect Linaro Member Companies will be eligible for one or more free passes depending on your membership tier and will also get a discounted rate for general tickets. You will soon receive communication from our Events team with your Connect conference registration code via the usual channels. As discussed during our face-to-face partner meeting last month, we are pleased to confirm that we will hold the next Linaro Partner Meeting the same week as Connect. LPM will start on Monday April 24th at 1pm and will end on Tuesday evening. It will be open to all Core, Club, Group and Project members. Connect will then follow on Wednesday through Friday. I am sending a calendar invite for LPM as a placeholder for your convenience, more details will follow in January. All attendees can start booking a room at the Park Plaza Riverbank using the Linaro group code [LINC23]. Please contact [59]connect(a)linaro.org if you have any issue with this code. In the booking page make sure you select the "Promotional Code" (and enter LINC23) in the "selected rate" field. [60]https://www.parkplazariverbank.com Best regards Andrea [61]Linaro Andrea Gallo | VP of Business Development T: +39.338.4075993 | [62]andrea.gallo(a)linaro.org T: +1 408 495 5430 | Skype: agallo70 (he / him / his) References 1. mailto:andrea.gallo@linaro.org 2. mailto:andrew.wafaa@arm.com 3. mailto:andy.harker@arm.com 4. mailto:anmar.oueja@linaro.org 5. mailto:atouzni@qti.qualcomm.com 6. mailto:bill.fletcher@linaro.org 7. mailto:craign@qti.qualcomm.com 8. mailto:daniel.thompson@linaro.org 9. mailto:davide.ricci@huawei.com 10. mailto:don.harbin@linaro.org 11. mailto:ebba.simpson@linaro.org 12. mailto:eric.finco@st.com 13. mailto:fang.liu@cixcomputing.com 14. mailto:gen.shimada@linaro.org 15. mailto:grant.likely@linaro.org 16. mailto:hans.tan@zeku.com 17. mailto:james.king@arm.com 18. mailto:jammy.zhou@cixcomputing.com 19. mailto:jason.martin1@nxp.com 20. mailto:jered@redhat.com 21. mailto:joakim.bech@linaro.org 22. mailto:joe.bates@linaro.org 23. mailto:jonathan.cameron@huawei.com 24. mailto:jonmasters@google.com 25. mailto:joyce.qi@linaro.org 26. mailto:kangkang.shen@futurewei.com 27. mailto:kshen@futurewei.com 28. mailto:leendert@qti.qualcomm.com 29. mailto:leonardo.garcia@linaro.org 30. mailto:li.gong@linaro.org 31. mailto:loic.pallardy@st.com 32. mailto:lwikeliu@qti.qualcomm.com 33. mailto:marcus.perryman@microsoft.com 34. mailto:mark.hambleton@arm.com 35. mailto:michael.wangke@huawei.com 36. mailto:mike.holmes@linaro.org 37. mailto:nicolas.dechesne@linaro.org 38. mailto:owada.kiyoshi@socionext.com 39. mailto:pbrobinson@redhat.com 40. mailto:rajav@quicinc.com 41. mailto:ramih@qti.qualcomm.com 42. mailto:randy.linnell@linaro.org 43. mailto:rob.booth@linaro.org 44. mailto:robert.oshana@nxp.com 45. mailto:ryan.arnold@linaro.org 46. mailto:ryu.real@samsung.com 47. mailto:scott.bambrough@linaro.org 48. mailto:seanr@quicinc.com 49. mailto:sellaiah@google.com 50. mailto:ssinghai@quicinc.com 51. mailto:tim.benton@linaro.org 52. mailto:tkjos@google.com 53. mailto:tom.gall@linaro.org 54. mailto:tomase@xilinx.com 55. mailto:tsoni@quicinc.com 56. mailto:yang.zhang@96boards.org 57. mailto:k-hirai@fujitsu.com 58. https://www.linaro.org/connect 59. mailto:connect@linaro.org 60. https://www.parkplazariverbank.com/ 61. https://www.linaro.org/ 62. mailto:andrea.gallo@linaro.org

2 years, 12 months

1
0
0 0

Re: Linaro-open-discussions Digest, Vol 25, Issue 3

by Joyce Qi

Hi Jonathan,Lorenzo,all, Do we have any topic to sync on our LOD meeting next week? Thanks:) Joyce > 在 2022年10月18日，上午8:00，linaro-open-discussions-request@op-lists.linaro.org 写道： > > Send Linaro-open-discussions mailing list submissions to > linaro-open-discussions(a)op-lists.linaro.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > linaro-open-discussions-request(a)op-lists.linaro.org > > You can reach the person managing the list at > linaro-open-discussions-owner(a)op-lists.linaro.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Linaro-open-discussions digest..." > > Today's Topics: > > 1. Re: Invitation: Linaro Open Discussions monthly meeting @ Wed 5 Oct 2022 19:00 - 20:00 (HKT) (linaro-open-discussions(a)op-lists.linaro.org) > (Salil Mehta) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Oct 2022 16:12:26 +0000 > From: Salil Mehta <salil.mehta(a)huawei.com> > Subject: [Linaro-open-discussions] Re: Invitation: Linaro Open > Discussions monthly meeting @ Wed 5 Oct 2022 19:00 - 20:00 (HKT) > (linaro-open-discussions(a)op-lists.linaro.org) > To: "joyce.qi(a)linaro.org" <joyce.qi(a)linaro.org>, "james.morse(a)arm.com" > <james.morse(a)arm.com> > Cc: "linaro-open-discussions(a)op-lists.linaro.org" > <linaro-open-discussions(a)op-lists.linaro.org>, > "lorenzo.pieralisi(a)linaro.org" <lorenzo.pieralisi(a)linaro.org>, > "ilkka(a)os.amperecomputing.com" <ilkka(a)os.amperecomputing.com>, > Jean-Philippe Brucker <jean-philippe.brucker(a)arm.com>, > "salil.mehta(a)opnsrc.net" <salil.mehta(a)opnsrc.net> > Message-ID: <12408d4c06604dd4bd8e017adf7e5fe6(a)huawei.com> > Content-Type: text/plain; charset="utf-8" > > Hi James, > As discussed in the meeting below are the repositories which you might want to have a look. > > [1] Forward ported QEMU with some fixes was shared (by Salil) > https://github.com/salil-mehta/qemu.git virt-cpuhp-armv8/rfc-v1-port29092022 > > [2] James Approach with online-capable and present==possible (some fixes) > https://github.com/salil-mehta/linux.git virt-cpuhp-arm64/rfc-v2/jmorse-pres-eq-poss-cpu > > [3] Variant of James approach with online-capable and conditionally present cpus > https://github.com/salil-mehta/linux.git virt-cpuhp-arm64/rfc-v2/jmorse-variant-with-cond-present-cpu > > I have also shared the LOD presentation with Joyce for uploading to the site. > > Attachment: > [1] Linaro Open Discussion Meeting Update - 05102022 - Salil_Mehta-fixed.pdf > > > Many thanks > Salil > >> -----Original Message----- >> From: Google Calendar [mailto:calendar-notification@google.com] On Behalf Of >> Joyce Qi via Linaro-open-discussions >> Sent: Wednesday, October 5, 2022 9:31 AM >> To: linaro-open-discussions(a)op-lists.linaro.org; james.morse(a)arm.com; >> Jonathan Cameron <jonathan.cameron(a)huawei.com>; lorenzo.pieralisi(a)linaro.org; >> ilkka(a)os.amperecomputing.com >> Subject: [Linaro-open-discussions] Invitation: Linaro Open Discussions monthly >> meeting @ Wed 5 Oct 2022 19:00 - 20:00 (HKT) >> (linaro-open-discussions(a)op-lists.linaro.org) >> >> Linaro Open Discussions monthly meeting >> Wednesday 5 Oct 2022 ⋅ 19:00 – 20:00 >> Hong Kong Standard Time >> >> Location >> https://linaro-org.zoom.us/j/95682500341 >> https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9568250 >> 0341&sa=D&source=calendar&usd=2&usg=AOvVaw2JDK9LgOcXl2WanQ86Y-6h >> >> >> >> Joyce QI 邀请您参加预先安排的 Zoom 会议。 >> >> 加入 Zoom 会议 >> https://linaro-org.zoom.us/j/95682500341 >> >> 会议号：956 8250 0341 >> 手机一键拨号 >> +16699009128,,95682500341# 美国 (San Jose) >> +13462487799,,95682500341# 美国 (Houston) >> >> 根据您的位置拨号 >> +1 669 900 9128 美国 (San Jose) >> +1 346 248 7799 美国 (Houston) >> +1 253 215 8782 美国 (Tacoma) >> +1 646 558 8656 美国 (New York) >> +1 301 715 8592 美国 (Washington DC) >> +1 312 626 6799 美国 (Chicago) >> 888 788 0099 美国免费 >> 877 853 5247 美国免费 >> 会议号：956 8250 0341 >> 查找本地号码：https://linaro-org.zoom.us/u/ady2J9Zn7t >> >> Guests >> linaro-open-discussions(a)op-lists.linaro.org >> james.morse(a)arm.com >> jonathan.cameron(a)huawei.com >> lorenzo.pieralisi(a)linaro.org >> ilkka(a)os.amperecomputing.com >> View all guest info >> https://calendar.google.com/calendar/event?action=VIEW&eid=Mjg1MjNrNWtiMWxv >> cGlsYW8zb2hwa3E5cWFfMjAyMjA5MjdUMTEwMDAwWiBsaW5hcm8tb3Blbi1kaXNjdXNzaW9uc0B >> vcC1saXN0cy5saW5hcm8ub3Jn&tok=NTQjY184anE0dGh2ZTNuN3NlaThhMGpmazlwdXI3c0Bnc >> m91cC5jYWxlbmRhci5nb29nbGUuY29tY2JlMDNmZTk3ZTYzMGMyN2ExZDE2N2QyYjcwOTYxMjNi >> ODIwMjA0ZQ&ctz=Asia%2FHong_Kong&hl=en_GB&es=0 >> >> Reply for linaro-open-discussions(a)op-lists.linaro.org and view more details >> https://calendar.google.com/calendar/event?action=VIEW&eid=Mjg1MjNrNWtiMWxv >> cGlsYW8zb2hwa3E5cWFfMjAyMjA5MjdUMTEwMDAwWiBsaW5hcm8tb3Blbi1kaXNjdXNzaW9uc0B >> vcC1saXN0cy5saW5hcm8ub3Jn&tok=NTQjY184anE0dGh2ZTNuN3NlaThhMGpmazlwdXI3c0Bnc >> m91cC5jYWxlbmRhci5nb29nbGUuY29tY2JlMDNmZTk3ZTYzMGMyN2ExZDE2N2QyYjcwOTYxMjNi >> ODIwMjA0ZQ&ctz=Asia%2FHong_Kong&hl=en_GB&es=0 >> Your attendance is optional. >> >> ~~//~~ >> Invitation from Google Calendar: https://calendar.google.com/calendar/ >> >> You are receiving this email because you are an attendee of the event. To >> stop receiving future updates for this event, decline this event. >> >> Forwarding this invitation could allow any recipient to send a response to >> the organiser, be added to the guest list, invite others regardless of >> their own invitation status or modify your RSVP. >> >> Learn more https://support.google.com/calendar/answer/37135#forwarding >> -- >> Linaro-open-discussions mailing list -- >> linaro-open-discussions(a)op-lists.linaro.org >> https://collaborate.linaro.org/display/LOD/Linaro+Open+Discussions+Home > > ------------------------------ > > Subject: Digest Footer > > Linaro-open-discussions mailing list -- linaro-open-discussions(a)op-lists.linaro.org > To unsubscribe send an email to linaro-open-discussions-leave(a)op-lists.linaro.org > > > ------------------------------ > > End of Linaro-open-discussions Digest, Vol 25, Issue 3 > ******************************************************

3 years

8
25
0 0

ACPICA support for generating MPAM tables?

by Hesham Almatary

Hello, I wonder if there's any code/support I can use to generate MPAM ACPI tables? Regards, Hesham

3 years

2
3
0 0

Invitation: Bigtop/OpenEuler Discussion @ Wed Dec 14, 2022 10am - 10:40am (CST) (linaro-open-discussions@op-lists.linaro.org)

by guodong.xu＠linaro.org

Bigtop/OpenEuler Discussion Wednesday Dec 14, 2022 ⋅ 10am – 10:40am China Standard Time - Shanghai Location https://linaro-org.zoom.us/j/98349251580 https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9834925… Hi, AllThis is an open discussion about making Bigtop to support OpenEuler release. You are welcomed to join. OpenEuler BigData SIG engineers will introduce their recent progress in this call.BR,Guodong Xu──────────Guodong Xu is inviting you to a scheduled Zoom meeting.Join Zoom Meetinghttps://linaro-org.zoom.us/j/98349251580Meeting ID: 983 4925 1580One tap mobile+16694449171,,98349251580# US+16699009128,,98349251580# US (San Jose)Dial by your location        +1 669 444 9171 US        +1 669 900 9128 US (San Jose)        +1 253 205 0468 US        +1 253 215 8782 US (Tacoma)        +1 346 248 7799 US (Houston)        +1 719 359 4580 US        +1 312 626 6799 US (Chicago)        +1 360 209 5623 US        +1 386 347 5053 US        +1 507 473 4847 US        +1 564 217 2000 US        +1 646 558 8656 US (New York)        +1 646 931 3860 US        +1 689 278 1000 US        +1 301 715 8592 US (Washington DC)        +1 305 224 1968 US        +1 309 205 3325 US        877 853 5247 US Toll-free        888 788 0099 US Toll-freeMeeting ID: 983 4925 1580Find your local number: https://linaro-org.zoom.us/u/abdNf0cim────────── Organizer guodong.xu(a)linaro.org guodong.xu(a)linaro.org Guests guodong.xu(a)linaro.org - organizer linaro-open-discussions(a)op-lists.linaro.org View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=Nzh1OHY0aTIwbWdu… Reply for linaro-open-discussions(a)op-lists.linaro.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=Nzh1OHY0aTIwbWdu… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

3 years

2
1
0 0

Re: Linaro-open-discussions Digest, Vol 25, Issue 9

by Joyce Qi

Hi Lorenzo, I have noticed you are in holiday on Nov,1st. I can switch the meeting to Nov 2nd if other people are free. @Lorenzo,James, Can we arrange Zhangfei’s questions( TLB missing impact the performance in vsva/ sva) as below in next meeting. Or can you help involve any other experts focus on this? Appreciated so much for your help here. Thanks:) Joyce > 在 2022年10月28日，上午8:00，linaro-open-discussions-request@op-lists.linaro.org 写道： > > Send Linaro-open-discussions mailing list submissions to > linaro-open-discussions(a)op-lists.linaro.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > linaro-open-discussions-request(a)op-lists.linaro.org > > You can reach the person managing the list at > linaro-open-discussions-owner(a)op-lists.linaro.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Linaro-open-discussions digest..." > > Today's Topics: > > 1. Re: Linaro-open-discussions Digest, Vol 25, Issue 3 (Zhangfei Gao) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 27 Oct 2022 12:06:59 +0800 > From: Zhangfei Gao <zhangfei.gao(a)linaro.org> > Subject: [Linaro-open-discussions] Re: Linaro-open-discussions Digest, > Vol 25, Issue 3 > To: Joyce Qi <joyce.qi(a)linaro.org>, Lorenzo Pieralisi > <lorenzo.pieralisi(a)linaro.org>, jean-philippe > <jean-philippe(a)linaro.org> > Cc: linaro-open-discussions(a)op-lists.linaro.org, linux(a)armlinux.org.uk > Message-ID: <2fba7536-1475-4755-9084-a920addecc42(a)linaro.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, Lorenzo > > When we debug vsva, sva on guest with 2-stage translation, > we found tlb miss impact performance a lot, with Jean's help. > > Currently we are using huge page feature in glibc to overcome this issue. > With huge page, vsva in guest can achieve comparable performance as sva > in host. > > More details: https://docs.qq.com/doc/DRXlpQmpTSlBZTGZZ > Will do some > > Basically we are using two optimization methods/ > host sva: using memset fist to overcome io page fault, since cpu alloc > physical memory is much faster than smmu. > guest vsva: using huge page to overcome tlbmiss. > > The customer are asking whether (next version) silicon (smmu) can do > some help to concur tlb miss issue or io page fault issue. > If so, software can be simpler. > Any suggestions? > > Thanks > > > On 2022/10/20 下午8:47, Joyce Qi via Linaro-open-discussions wrote: >> Hi Jonathan,Lorenzo,all, >> >> Do we have any topic to sync on our LOD meeting next week? >> >> Thanks:) >> Joyce >> >> >> > > > ------------------------------ > > Subject: Digest Footer > > Linaro-open-discussions mailing list -- linaro-open-discussions(a)op-lists.linaro.org > To unsubscribe send an email to linaro-open-discussions-leave(a)op-lists.linaro.org > > > ------------------------------ > > End of Linaro-open-discussions Digest, Vol 25, Issue 9 > ******************************************************

3 years

6
16
0 0

FYI, regarding the _STA.present changes after _EJx method

by Salil Mehta

Hi James, I am doing changes(both ACPI interface and QoM - some prototyping required) in the Qemu to reflect the _STA.present correctly after _EJx method has been evaluated. Will get back to you later this week. I hope this is not blocking you in any way? Thanks Salil

3 years, 1 month

1
1
0 0

Linaro OP-TEE Contribution (LOC) monthly meeting November 22

by Jens Wiklander

Hi, For time and connection details see the calendar at https://www.trustedfirmware.org/meetings/ I have one topic for the LOC: Can we deprecate paging of OP-TEE on Armv8-A platforms using FF-A? Any other topic? Thanks, Jens

3 years, 1 month

1
0
0 0

[Question] Regarding immediate value assigned to 'hypercall.nr' and its corresponding userspace check

by Salil Mehta

Hi James, Question: We are using HVC conduit for PSCI, do we need a check if hypercall being trapped to userspace is SMC or HVC? File: linux/arch/arm64/kvm/hypercalls.c (your code change) int kvm_hvc_user(struct kvm_vcpu *vcpu) { [...] run->exit_reason = KVM_EXIT_HYPERCALL; run->hypercall.nr = kvm_vcpu_hvc_get_imm(vcpu); -> this would be referred by userspace code? /* Add the first parameters for fast access. */ [...] return 0; } # Userspace Code Excerpt (JPB's June 2021 code reference) In the userspace, a check similar to below might be required I guess: + /* Under KVM, the PSCI conduit is HVC */ + if (imm & KVM_ARM_EXIT_HYPERCALL_SMC) { + XXXX_log_mask("%s: unexpected SMC exit\n", __func__); + return 0; + } + +/* + * In kvm_run::hypercall::nr, this bit indicates that the call is a SMC. When + * the bit is not set, the call is an HVC. + */ +#define KVM_ARM_EXIT_HYPERCALL_SMC (1ULL << 63) + I am being lazy but Could you please provide more clarification on the use of 'hypercall.nr' for this check? [1] https://developer.arm.com/documentation/ddi0596/2021-12/Base-Instructions/H… [HVC #0] Thanks Salil

3 years, 1 month

2
3
0 0

Enabling/Disabling vCPUs and Qemu 'coldplug'

by James Morse

Hi Salil(s), You mentioned 'cold plug behaves differently'. From the last call you described 'coldplug' as starting Qemu with '-S' so it doesn't actually run the guest, then adding vCPUs before releasing Qemu to run the guest. You said CPUs added this way can't be disabled. (am I right so far?) This turns out to be a bit murkier than that. You can disable these vCPUs, but the first call will fail. The reason is very simple: Qemu is sending a device-check for the first call, not an eject-request. Linux prints a warning for the spurious device-check because the CPU already exists and is even online. An example flow, with the below debug[0], is: # qemu -S smp cpus=1,maxcpus=3,cores=3,threads=1,sockets=1 ${REST_OF_OPTIONS} On the Qemu monitor: | device_add driver=host-arm-cpu,core-id=1,id=cpu1 | cont [Qemu boots the guest] acpi_processor_add() is called twice during boot, once for vCPU0 and once for the vCPU that was 'coldplugged' vCPU1. On the Qemu monitor: | device_del cpu1 [ 56.427089] ACPI: XYZZY:ACPI_NOTIFY_DEVICE_CHECK on ACPI0007:1 [ 56.428239] ACPI: XYZZY: acpi_scan_device_check() 1 | 1 [ 56.429335] CPU: 1 PID: 105 Comm: kworker/u6:2 Not tainted 6.1.0-rc2-00028-g6eaecb5ffd26-dirty #14644 [ 56.431043] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 56.432431] Workqueue: kacpi_hotplug acpi_hotplug_work_fn [ 56.433520] Call trace: [ 56.434015] dump_backtrace.part.0+0xe0/0xf0 [ 56.434875] show_stack+0x18/0x40 [ 56.435546] dump_stack_lvl+0x68/0x84 [ 56.436308] dump_stack+0x18/0x34 [ 56.436983] acpi_device_hotplug+0x234/0x4e0 [ 56.437847] acpi_hotplug_work_fn+0x24/0x40 [ 56.438695] process_one_work+0x1d0/0x320 [ 56.439515] worker_thread+0x14c/0x444 [ 56.440283] kthread+0x10c/0x110 [ 56.440935] ret_from_fork+0x10/0x20 [ 56.441680] acpi ACPI0007:01: Already enumerated [ This is because Qemu is adding a CPU that already exists ] A definition of madness is doing the same thing and expecting a different result. On the Qemu monitor: | device_del cpu1 [ 67.723708] ACPI: XYZZY:ACPI_NOTIFY_EJECT_REQUEST on ACPI0007:1 [ 67.771014] psci: CPU1 killed (polled 0 ms) [ 67.773437] XYZZY: acpi_processor_post_eject() It looks like Qemu creates the device-check when you cold-plug the vCPU, but doesn't deliver it, instead it delivers it _instead_ of the next notification. Qemu v7.1.0 for doesn't do this for x86, nor does it deliver the spurious ACPI_NOTIFY_DEVICE_CHECK early. I'd suggest the arm64 changes are generating a ACPI_NOTIFY_DEVICE_CHECK when it shouldn't. Thanks, James [0] Debug diff --git a/drivers/acpi/acpi_processor.c b/drivers/acpi/acpi_processor.c index a4d58e0d1452..ec72f2d2a5fb 100644 --- a/drivers/acpi/acpi_processor.c +++ b/drivers/acpi/acpi_processor.c @@ -492,6 +496,8 @@ static void acpi_processor_post_eject(struct acpi_device *device) unsigned long long sta; acpi_status status; + pr_err("XYZZY: acpi_processor_post_eject()\n"); + if (!device) return; diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c index d466c8195314..f9f4c7707886 100644 --- a/drivers/acpi/bus.c +++ b/drivers/acpi/bus.c @@ -467,43 +467,55 @@ static void acpi_bus_notify(acpi_handle handle, u32 type, void *data) u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE; bool hotplug_event = false; + adev = acpi_get_acpi_dev(handle); + if (!adev) + goto err; + switch (type) { case ACPI_NOTIFY_BUS_CHECK: acpi_handle_debug(handle, "ACPI_NOTIFY_BUS_CHECK event\n"); + pr_err("XYZZY:ACPI_NOTIFY_BUS_CHECK on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); hotplug_event = true; break; case ACPI_NOTIFY_DEVICE_CHECK: acpi_handle_debug(handle, "ACPI_NOTIFY_DEVICE_CHECK event\n"); + pr_err("XYZZY:ACPI_NOTIFY_DEVICE_CHECK on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); hotplug_event = true; break; case ACPI_NOTIFY_DEVICE_WAKE: acpi_handle_debug(handle, "ACPI_NOTIFY_DEVICE_WAKE event\n"); + pr_err("XYZZY:ACPI_NOTIFY_DEVICE_WAKE on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); break; case ACPI_NOTIFY_EJECT_REQUEST: acpi_handle_debug(handle, "ACPI_NOTIFY_EJECT_REQUEST event\n"); + pr_err("XYZZY:ACPI_NOTIFY_EJECT_REQUEST on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); hotplug_event = true; break; case ACPI_NOTIFY_DEVICE_CHECK_LIGHT: acpi_handle_debug(handle, "ACPI_NOTIFY_DEVICE_CHECK_LIGHT event\n"); + pr_err("XYZZY:ACPI_NOTIFY_DEVICE_CHECK_LIGHT on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); /* TBD: Exactly what does 'light' mean? */ break; case ACPI_NOTIFY_FREQUENCY_MISMATCH: acpi_handle_err(handle, "Device cannot be configured due " "to a frequency mismatch\n"); + pr_err("XYZZY:ACPI_NOTIFY_FREQUENCY_MISMATCH on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); break; case ACPI_NOTIFY_BUS_MODE_MISMATCH: acpi_handle_err(handle, "Device cannot be configured due " "to a bus mode mismatch\n"); + pr_err("XYZZY:ACPI_NOTIFY_BUS_MODE_MISMATCH on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); break; case ACPI_NOTIFY_POWER_FAULT: acpi_handle_err(handle, "Device has suffered a power fault\n"); + pr_err("XYZZY:ACPI_NOTIFY_POWER_FAULT on %s:%s\n", acpi_device_hid(adev), acpi_device_uid(adev)); break; default: @@ -511,10 +523,6 @@ static void acpi_bus_notify(acpi_handle handle, u32 type, void *data) break; } - adev = acpi_get_acpi_dev(handle); - if (!adev) - goto err; - if (adev->dev.driver) { struct acpi_driver *driver = to_acpi_driver(adev->dev.driver); diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c index 2d1a82aa1607..b2bc1c611a83 100644 --- a/drivers/acpi/scan.c +++ b/drivers/acpi/scan.c @@ -380,6 +380,8 @@ static int acpi_scan_device_check(struct acpi_device *adev) { int error; + pr_err("XYZZY: acpi_scan_device_check() %u | %u\n", adev->status.present, adev->status.functional); + acpi_bus_get_status(adev); if (adev->status.present || adev->status.functional) { /* @@ -391,6 +393,7 @@ static int acpi_scan_device_check(struct acpi_device *adev) * again). */ if (adev->handler) { + dump_stack(); dev_warn(&adev->dev, "Already enumerated\n"); return -EALREADY; }

3 years, 1 month

2
2
0 0

Linaro Bigtop OpenEuler distribution discussion

by Guodong Xu

Hi, All We are working on bringing OpenEuler to the Bigtop's support distribution list. This call is to cover the current issues we have found. Welcome to join the discussion. Meeting details: https://linaro-org.zoom.us/j/99353492289 <https://linaro-org.zoom.us/j/99353492289>Meeting ID: 993 5349 2289 Friday, November 4⋅10:30 – 11:30am (UTC/GMT+8 time zone) Topics: 1. "gpdb5.28.5 needs to support python3 version in OpenEuler" https://issues.apache.org/jira/browse/BIGTOP-3860 2. "Solr smoke test failed in OpenEuler" https://issues.apache.org/jira/browse/BIGTOP-3859 Thanks. Best regards, Guodong Xu on behalf of the Linaro Team.

3 years, 1 month

1
0
0 0

2025

2024

2023

2022

2021

2020

Linaro-open-discussions