lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH0PR02MB807367CCAD0D5938C4679E18F6E7A@CH0PR02MB8073.namprd02.prod.outlook.com>
Date:   Tue, 29 Aug 2023 15:10:34 +0000
From:   Pawandeep Oza <poza@....qualcomm.com>
To:     'Sudeep Holla' <sudeep.holla@....com>,
        "Pawandeep Oza (QUIC)" <quic_poza@...cinc.com>
CC:     "rafael@...nel.org" <rafael@...nel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: RE: ACPI binding with SCMI

I am looking for scmi binding to ACPI. Basically, SCMI based perf control. 
We have ACPI based system, so I am looking for where I can describe (some way to describe doorbell and share memory in ACPI), 
and then scmi perf can bind to it via some sort of transport (perhaps fastchannels ? )

Regards,
Oza.
-----Original Message-----
From: Sudeep Holla <sudeep.holla@....com> 
Sent: Tuesday, August 29, 2023 2:19 AM
To: Pawandeep Oza (QUIC) <quic_poza@...cinc.com>
Cc: rafael@...nel.org; Sudeep Holla <sudeep.holla@....com>; linux-arm-kernel@...ts.infradead.org; linux-kernel@...r.kernel.org; linux-acpi@...r.kernel.org
Subject: Re: ACPI binding with SCMI

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

On Fri, Aug 25, 2023 at 09:34:59PM +0000, Pawandeep Oza (QUIC) wrote:

[...]

>
> But I still fail to see how fastchannel doorbell and shared memory 
> space could get bind to PCC space (type 3) ? I am on 6.3 kernel.

They simply don't bind to PCC, PCC can't be fast channel. What exactly are you looking for here ? If you provide more details on that, I can see if I can help or suggest or may be explore along with you if the solution doesn't exists yet.

--
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ