Re: MTE enabled hardware

Sat, 01 Oct 2022 06:20:25 -0700 


> On 1. Oct 2022, at 15:15, 'Dmitry Vyukov' via address-sanitizer 
> <[email protected]> wrote:
> 
> On Sat, 1 Oct 2022 at 14:25, 'Koschel, J. (Jakob)' via
> address-sanitizer <[email protected]> wrote:
>> 
>> Hey,
>> 
>> it was worth a shot, after Dmitry suggested to try here ;)
>> Regardless thanks for your reply, I guess I'll have to wait a bit more.
> 
> Just in case: you considered using qemu, right?

yes! But for performance evaluation we are trying to run it on real hardware.

> 
>>> On 30. Sep 2022, at 01:26, Konstantin Serebryany 
>>> <[email protected]> wrote:
>>> 
>>> Hi Jakob!
>>> 
>>> Thanks for your interest.
>>> Unfortunately, we are not aware of any publicly available device with 
>>> usable MTE.
>>> Please pester your hardware suppliers directly, or wait :)
>>> 
>>> --kcc
>>> 
>>> 
>>> 
>>> On Thu, Sep 29, 2022 at 3:08 PM 'Jakob K.' via address-sanitizer 
>>> <[email protected]> wrote:
>>> Hi all,
>>> 
>>> I'm currently looking into MTE and therefore inevitably also at the great 
>>> work on MemTagSanitizer & KASAN_HW_TAGS.
>>> 
>>> Since you guys are working on this: do you happen to know if there is any 
>>> hardware out on the market you are using for testing MTE?
>>> 
>>> I've been looking at the Samsung S22 with the exynos2200 which does support 
>>> MTE. Unfortunately it looks like the bootloader (in connection with "Exynos 
>>> Secure Monitor") is responsible to setup the DRAM locations to store the 
>>> tags & this doesn't seem to be enabled. This results in MTE working *until* 
>>> the tagged memory is evicted from the cache. Once the memory is brought 
>>> back into the cache it forgot that it was tagged :/
>>> 
>>> If you know of any hardware out there that you might have tested with MTE, 
>>> I'd appreciated some pointers!
>>> 
>>> Thank you!
>>> Jakob
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "address-sanitizer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/address-sanitizer/01cba890-7360-4dc5-a45b-7265d14c4195n%40googlegroups.com.
>>> 
>>> --
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "address-sanitizer" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/address-sanitizer/o-qhiTBFlBc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/address-sanitizer/CAGQ9bdxJM_eXgFQm_Wq%2BNyF-_p0XXVQChOGN08J6%3D%3Dok_8SPGw%40mail.gmail.com.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "address-sanitizer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/address-sanitizer/62531A20-0374-4463-AFE8-0D3CB380A388%40vu.nl.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "address-sanitizer" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/address-sanitizer/o-qhiTBFlBc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/address-sanitizer/CACT4Y%2BZGf%3Dyp61Sw_W6MPGe-KCd4Hy%2BOUnAUR0QWyQBzL5OSSg%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/address-sanitizer/DB86FDF6-F82A-4A24-9B74-4AB82B8B33F0%40vu.nl.






















					Reply via email to