-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sun, May 21, 2023 at 01:40:31PM +1000, William ML Leslie wrote:
Hello,
I just noticed in the new x86-S rfc that Intel published that there will be no further support for io port access for processes in ring 3. Thankfully, this doesn't look like it will impact seL4, which provides capabilities to special objects representing port ranges on x86, which are then implemented in the kernel. Just in case anyone was wondering if there will be any impact, since this is the one thing that stuck out to me.
Here's Intel's RFC:
https://www.intel.com/content/www/us/en/developer/articles/technical/envisio...
I think I might steal your IO port API for newer versions of Coyotos, which /is/ impacted by the change. TBF, I think seL4 has a better IRQ handling interface than the one we currently have too. I guess it's only fair it goes both ways!
(Off-topic) Where can I find information on Coyotos? What advantages does it have over seL4, and do you plan to formally verify it in the future? - -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmRppQUACgkQsoi1X/+c IsE8gRAAtBwtqKmd2q8jXokvebHNXBe2Stm14twkVGUrSEZN2t6CVOjwI11rFdH8 WQ0x/sUfBvHNIw9ggq/taRYAawYm5EsgOskETco1Kz1oNnzPD/euS74PY0cEP/et q283mdFzg2utTDNnlur/ZKqRT+VRH6WYK8CORJBbqpMeuMg0joPkCty5gIzzQB7L y09bvXEYksvAbaZ2DAunJ1t2ldeVHBvhvvkGINHtosn2hxQ0xgAXnfF0xr5K/lh3 YHqVevgAUuLWYuYbdQjQ3cUmduBUwhNRWmpS7ktbEhF31xQm5lBIO8QjVqMLdulT LUp+EnmCY9s+Ua76eedlLXUQUiiZBVdqhHSrMIWYvTfwoxPr+z0X0pELjllmsFoq 0Kk+6I36KNRUNg9rcGpGlOFvh9fYzIcq3rI0EdWgadklvPr1TiYCdt+7dRb2JXWG kZnMdWHrkhu8GmTnk4QX+YqUmx/7+MfhcBY0+xe3wXkuBc4gRqUk64LDCnkECWkB oeEBz5mBlq/nTPCT0sVokUdeWEfmK2AVDYpiJ4Gkqv4Ny/0TY9AqHy8q+DVonZcM VKu+qJfJp2xuMOXgAl6EAPSCn85ukmzyCgmwwgLsyReTuDq8GTWM4wATwT9sDB+6 kEWl+UyODsJi/V16evD9mUBpKmYThfoOOLqPMDh7ZW0AyJcKlZU= =qhke -----END PGP SIGNATURE-----