Hi Yabin,
Thanks for working to enable this on ARM64 and test the performance on Android!
Please see my comments below.
Thanks,
-Rong
On Thu, Nov 14, 2024 at 9:11 PM Yabin Cui wrote:
>
> Select ARCH_SUPPORTS_AUTOFDO_CLANG to allow AUTOFDO_CLANG to be
> selected.
>
> On ARM64, ETM traces can be
Select ARCH_SUPPORTS_AUTOFDO_CLANG to allow AUTOFDO_CLANG to be
selected.
On ARM64, ETM traces can be recorded and converted to AutoFDO profiles.
Experiments on Android show 4% improvement in cold app startup time
and 13% improvement in binder benchmarks.
Signed-off-by: Yabin Cui
---
Documentat
Hi Deepak
On Thu, Nov 14, 2024 at 11:50 PM Deepak Gupta wrote:
>
>
> Hi Nick,
>
> Thanks for reviewing and helping.
>
> On Thu, Nov 14, 2024 at 02:17:30PM +0800, Nick Hu wrote:
> >Hi Deepak
> >
> >On Thu, Nov 14, 2024 at 9:25 AM Deepak Gupta wrote:
> >>
> >> On Thu, Nov 14, 2024 at 09:20:14AM +0
The Code of Conduct committee's goal first and foremost is to bring about
change to ensure our community continues to foster respectful discussions.
In the interest of transparency, the CoC enforcement policy is formalized
for unacceptable behaviors.
Update the Code of Conduct Interpretation docu
On Wed, Nov 13, 2024 at 07:18:42PM -0800, Nicolin Chen wrote:
> > so the user would try to create vDevices with a given viommu_obj until
> > failure, then it would allocate another viommu_obj for the failed device.
> > is it? sounds reasonable.
>
> Yes. It is the same as previously dealing with a
Hi Nick,
Thanks for reviewing and helping.
On Thu, Nov 14, 2024 at 02:17:30PM +0800, Nick Hu wrote:
Hi Deepak
On Thu, Nov 14, 2024 at 9:25 AM Deepak Gupta wrote:
On Thu, Nov 14, 2024 at 09:20:14AM +0800, Nick Hu wrote:
>Hi Deepak
>
>On Thu, Nov 14, 2024 at 9:06 AM Deepak Gupta wrote:
>>
On Wed, Nov 13, 2024 at 04:25:57PM -0700, Shuah Khan wrote:
> +The scope of the ban for a period of time could include:
> +
> +a. denying patch contributions and pull requests
> +b. pausing collaboration with the violator by ignoring their
> + contributions and/or blocking their email
On Wed, Nov 13, 2024 at 12:59 PM Paolo Bonzini wrote:
>
> On 11/13/24 17:24, Doug Covelli wrote:
> >> No worries, you're not hijacking :) The only reason is that it would
> >> be more code for a seldom used feature and anyway with worse performance.
> >> (To be clear, CR8 based accesses are allowe
On Thu, Nov 14, 2024 at 08:01:34AM -0700, Shuah Khan wrote:
> > c. restricting their ability to communicate via kernel.org platforms,
> > such as mailing lists and social media sites
> >
> > It makes more sense to phrase it this way, because it's really the
> > communication that is t
On 11/14/24 07:38, Konstantin Ryabitsev wrote:
On Wed, Nov 13, 2024 at 04:25:57PM -0700, Shuah Khan wrote:
+The scope of the ban for a period of time could include:
+
+a. denying patch contributions and pull requests
+b. pausing collaboration with the violator by ignoring their
+ c
10 matches
Mail list logo