Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

90 participants
7134 discussions

by foltzbutman＠gmail.com

在線購買香港身份證和駕駛執照（微信ID：Wesbutman）在線購買中國身份證和駕駛執照. 在線購買韓國身份證和駕駛執照. 線上購買台灣身分證和駕駛執照. 在線購買泰國身份證和駕駛執照. 在線購買日本身份證和駕駛執照.(WhatsApp：+49 1521 5066462) 在線購買美國身份證和駕駛執照. 在線購買波蘭身份證和駕駛執照. 在線購買身份證和駕駛執照. 在線購買英國身份證和駕駛執照. 在線購買加拿大身份證和駕駛執照. 在線購買挪威身份證和駕駛執照. 在線購買馬來西亞身份證和駕駛執照. 在線購買法國身份證和駕駛執照. 在線購買捷克身份證和駕駛執照. 在線購買巴西身份證和駕駛執照. 在線購買愛沙尼亞身份證和駕駛執照.(WhatsApp：+49 1521 5066462) 在線購買雅思證書。在線購買托福證書。在線購買PTE證書。在線購買ESOL證書。在線購買GRE證書。在線購買CELPIP證書。在線購買GMAT證書。在線… 购买中国驾驶执照: https://firstdocumentsonline.com/购买中国驾驶执照/ 购买中国身份证: https://firstdocumentsonline.com/购买中国身份证/ 購買韓國身分證: https://firstdocumentsonline.com/購買韓國身分證/ 在線購買日本身份證: https://firstdocumentsonline.com/在線購買日本身份證/ 線上購買台灣身分證: https://firstdocumentsonline.com/線上購買台灣身分證/ 購買韓國身分證: https://firstdocumentsonline.com/buy-korean-id-card/ 購買美國駕照: https://firstdocumentsonline.com/buy-u-s-drivers-license-2/ 在線購買真正的台灣駕照: https://firstdocumentsonline.com/在線購買真正的台灣駕照/ 在线购买意大利驾驶执照: https://firstdocumentsonline.com/在线购买意大利驾驶执照/ 在线购买奥地利驾驶执照: https://firstdocumentsonline.com/在线购买奥地利驾驶执照/ 在线购买欧盟驾驶执照: https://firstdocumentsonline.com/在线购买欧盟驾驶执照/ 在线购买德国驾驶执照: https://firstdocumentsonline.com/在线购买德国驾驶执照/ 購買加拿大永久居民卡: https://firstdocumentsonline.com/購買加拿大永久居民卡/ (WhatsApp：+49 1521 5066462) (微信 ID：Wesbutman) (Telegram：wesbutman0) (信箱：wesbutman0(a)gmail.com) https://firstdocumentsonline.com/ 在線購買阿拉巴馬州駕照。在線購買阿拉斯加州駕照。在線購買亞利桑那州駕照。(WhatsApp：+49 1521 5066462) 在線購買阿肯色州駕照。在線購買加州駕照。在線購買科羅拉多州駕照。在線購買康涅狄格州駕照。在線購買特拉華州駕照。在線購買佛羅裡達州駕照。在線購買佐治亞州駕照。在線購買夏威夷州駕照。在線購買愛達荷州駕照。在線購買伊利諾伊州駕照。在線購買印第安納州駕照。在線購買愛荷華州駕照。在線購買堪薩斯州駕照。在線購買肯塔基州駕照。在線購買路易斯安那州駕照。在線購買緬因州駕照。在線購買馬裡蘭州駕照。在線購買馬薩諸塞州駕照。在線購買密西根州駕照。在線購買明尼蘇達州駕照。(WhatsApp：+49 1521 5066462) 在線購買密西西比州駕照。在線購買密蘇裡州駕照。在線購買蒙大拿州駕照。在線購買內布拉斯加州駕照。在線購買內華達州駕照。在線購買新罕布什爾州駕照。在線購買新澤西州駕照。在線購買新墨西哥州駕照。在線購買紐約州駕照。在線購買北卡羅來納州駕照。在線購買北達科他州駕照。在線購買俄亥俄州駕照。在線購買俄克拉荷馬州駕照。在線購買俄勒岡州駕照。在線購買賓州駕照。在線購買羅德島州駕照。在線購買南卡羅來納州駕照。在線購買南達科他州駕照。在線購買田納西州駕照。在線購買德克薩斯州駕照。(WhatsApp：+49 1521 5066462) 在線購買猶他州駕照。在線購買佛蒙特州駕照。在線購買弗吉尼亞州駕照。在線購買華盛頓州駕照。在線購買西維吉尼亞州駕照。在線購買威斯康辛州駕照。在線購買懷俄明州駕照。購買美國駕照: https://firstdocumentsonline.com/buy-u-s-drivers-license-2/ 在线购买波兰驾驶执照: https://firstdocumentsonline.com/在线购买波兰驾驶执照/ 在线购买瑞典驾驶执照: https://firstdocumentsonline.com/在线购买瑞典驾驶执照/ 在线购买瑞士驾驶执照: https://firstdocumentsonline.com/在线购买瑞士驾驶执照/ 在线购买英国驾驶执照: https://firstdocumentsonline.com/在线购买英国驾驶执照/ 在线购买爱尔兰驾驶执照: https://firstdocumentsonline.com/在线购买爱尔兰驾驶执照/ 在線購買波蘭身份證: https://firstdocumentsonline.com/buy-polish-id-card/ 在線購買比利時身份證: https://firstdocumentsonline.com/buy-belgian-id-card/ 在線購買西班牙身份證: https://firstdocumentsonline.com/buy-spanish-id-card/ 在線購買義大利身份證: https://firstdocumentsonline.com/buy-italian-id-card/ 在線購買新加坡身份證: https://firstdocumentsonline.com/buy-singapore-id-card/ 在線購買歐盟居留許可: https://firstdocumentsonline.com/buy-an-eu-residence-permit-online/ (WhatsApp：+49 1521 5066462) (微信 ID：Wesbutman) (Telegram：wesbutman0) (信箱：wesbutman0(a)gmail.com) https://firstdocumentsonline.com/

3 days, 15 hours

by foltzbutman＠gmail.com

Compre pasaportes reales y falsos (WhatsApp: +49 1521 5066462), licencias de conducir, tarjetas de identificación; compre pasaportes legítimos de EE. UU., pasaportes chinos (ID de WeChat: Wesbutman), pasaportes canadienses, malasios, de Hong Kong y de Taiwán; pasaportes biométricos legítimos, pasaportes europeos y australianos; pasaportes registrados en bases de datos gubernamentales; permisos de residencia canadienses (tarjetas RP); obtenga ciudadanía estadounidense y tarjetas de residencia permanente (Green Cards); ¿dónde puedo conseguir un pasaporte? (Correo electrónico: wesbutman0(a)gmail.com); compre licencias de conducir en línea, renueve su pasaporte (ID de WeChat: Wesbutman). https://firstdocumentsonline.com/ https://firstdocumentsonline.com/ Compre dinero falso (WhatsApp: +49 1521 5066462). Compre dólares estadounidenses (USD) falsos, yuanes chinos (RMB/CNY) falsos, dólares canadienses (CAD) falsos, dólares australianos (AUD) falsos (WhatsApp: +49 1575 3756974), libras esterlinas (GBP) falsas, euros (EUR) falsos, dólares de Hong Kong (HK) falsos. Compre billetes falsos de alta calidad indetectables. https://firstdocumentsonline.com/counterfeit-money/ https://firstdocumentsonline.com/counterfeit-money/ Compre certificados TOEFL, IELTS, TOEIC (Correo electrónico: wesbutman0(a)gmail.com); compre ciudadanía canadiense o estadounidense; compre certificados canadienses TCF, TEF, CELPIP, Celta; obtenga residencia canadiense o inmigración directa a Canadá; compre licencia de conducir, tarjeta de identificación, tarjeta de residencia de EE. UU. (Green Card) (ID de WeChat: Wesbutman), número de Seguro Social (SSN), permiso de trabajo, nueva tarjeta de identificación, tarjeta de Seguro Nacional (NIN, SIN); compre certificado de matrimonio o certificado de nacimiento. Haga su pedido en línea (ID de WeChat: Wesbutman) https://buytraveldocsonline.com/ ¿Quiere comenzar una segunda vida con una nueva identidad? ¿Quiere proteger su privacidad, construir un nuevo historial crediticio, evitar las verificaciones de antecedentes penales y recuperar su libertad? (WhatsApp: +49 1521 5066462) (Correo electrónico: wesbutman0(a)gmail.com) Nuestra empresa cuenta con muchos años de experiencia en la elaboración de pasaportes falsos y otros documentos de identidad. Utilizamos equipos y materiales de alta calidad para producir estos pasaportes. Replicamos cuidadosamente todas las características de seguridad de los pasaportes auténticos para crear documentos falsos. Somos los mejores fabricantes de documentos de identidad falsos de alta calidad. (WhatsApp: +49 1521 5066462) (ID de WeChat: Wesbutman) (Telegram: wesbutman0) (Correo electrónico: wesbutman0(a)gmail.com) https://firstdocumentsonline.com/ https://firstdocumentsonline.com/ https://buytraveldocsonline.com/

3 days, 15 hours

by foltzbutman＠gmail.com

3 days, 15 hours

by foltzbutman＠gmail.com

在線購買雅思證書 (微信 ID：Wesbutman) 購買GREE、NCE、雅思、托福、PTE、CPSO、學位及其他文件。我們也提供文憑（NCE）（PMP、NEBOSH、NCLEX、CIPT）和其他語言證書（微信ID：Wesbutman）（雅思、PTE、CELPIP、歌德）（WhatsApp：+49 1521 5066462）。在線購買有效的雅思、歌德、托福、PTE、托業、CELPIP證書，立即購買NCLEX-RN和NCLEX-PN。對於有志成為美國註冊護理師的人來說，無需參加考試即可通過NCLEX至關重要。透過我們的綜合指南，探索通往成功護理職業生涯的道路。（WhatsApp：+49 1521 5066462） https://firstdocumentsonline.com/ 在新不倫瑞克省購買正版雅思和CELPIP證書，(微信ID：Wesbutman) 購買CELPIP證書，購買真實雅思證書，購買雅思，在西北地區購買註冊GRE證書。在加拿大新斯科細亞省購買正版GMAT證書 - 在新斯科細亞省無需考試即可購買CELPIP證書 - (微信 ID：Wesbutman) 在加拿大努納武特地區購買雅思、GRE、CELPIP、CISSP證書（郵箱：wesbutman0(a)gmail.com) 線上購買PTE證書、托福證書、(微信ID：Wesbutman) GMAT證書、CAE證書、SAT證書，出售已註冊的CELPIP證書，無需考試即可獲得PTE證書，購買正版NEBOSH證書，在線購買CAE證書，在線購買托福證書，出售已註冊的PMP證書，在線購買GRE證書，在線購買GMAT證書。購買正版雅思證書（WhatsApp：+49 1521 5066462），無需考試即可獲得NEBOSH證書。 https://firstdocumentsonline.com/buy-real-usa-passport/ https://firstdocumentsonline.com/buy-a-real-canadian-passport/ https://firstdocumentsonline.com/buy-real-chinese-passport/ https://firstdocumentsonline.com/buy-real-chinese-passport/ https://firstdocumentsonline.com/buy-real-korean-passport/ 購買真假護照, 購買正品美國護照、加拿大護照（微信ID：Wesbutman）、韓國護照、香港護照、台灣護照、中國護照、日本護照、泰國護照、波蘭護照、澳洲護照、英國護照（WhatsApp：+49 1521 5066462）、挪威護照、馬來西亞護照、法國護照、捷克護照、巴西護照、愛沙尼亞護照、身分證（真/假）、台灣身分證、(微信ID：Wesbutman)台灣駕照、泰國駕照、泰國證件（真/假）、簽證（真/假）、美元（假）、人民幣（ 5066462）.在線購買雅思證書。在線購買托福證書。在線購買PTE證書。在線購買ESOL證書。在線購買GRE證書。在線購買CELPIP證書。在線購買… (WhatsApp：+49 1521 5066462) (微信 ID：Wesbutman) (Telegram：wesbutman0) (信箱：wesbutman0(a)gmail.com) https://firstdocumentsonline.com/ https://buytraveldocsonline.com/

3 days, 15 hours

by foltzbutman＠gmail.com

Buy Passports online (WhatsApp: +49 1521 5066462), buy legitimate US passports, buy Chinese passports, (WeChat ID: Wesbutman), buy Canadian passports, buy Malaysian passports, buy Hong Kong passports, buy Taiwan passports, legitimate biometric passports, buy US passports,(WeChat ID: Wesbutman) buy European passports, buy Australian passports, buy passports registered in government databases, buy Canadian residence permits (RP cards), get US citizenship and green cards, where can I get a passport? (Email: wesbutman0(a)gmail.com), buy driver's license online, renew passport. (WeChat ID: Wesbutman) https://firstdocumentsonline.com/ https://firstdocumentsonline.com/ https://firstdocumentsonline.com/ Buy counterfeit money. (WhatsApp: +49 1521 5066462) Buy fake US dollars (USD), Buy fake Chinese yuan (RMB), buy counterfeit RMB (CNY), buy counterfeit RMB/RMB, Buy counterfeit money (CNY), buy counterfeit RMB/RMB, buy fake Canadian dollars (CAD), buy fake Australian dollars (AUD) (WhatsApp : +49 1521 5066462) Buy fake British pounds (GBP), buy fake Euros (EUR), buy fake Hong Kong dollars (HK). Buy high-quality undetected banknotes. https://firstdocumentsonline.com/counterfeit-money/ https://firstdocumentsonline.com/counterfeit-money/ Buy TOEFL, IELTS, TOEIC (Email: wesbutman0(a)gmail.com), buy Canadian citizenship, buy US citizenship, buy Canadian TCF, TEF, CELPIP, Celta certificates, Canadian residency, direct immigration to Canada, buy driver's license, ID card, buy US green card (WeChat ID: Wesbutman), buy Social Security Number (SSN), work permit, get a new ID card, National Insurance Card, NIN, SIN, buy SSN, buy marriage certificate, buy birth certificate. Order online (WeChat ID: Wesbutman) https://buytraveldocsonline.com/ Do you want to start a second life with a new identity? Protect your privacy, build a new credit history, bypass criminal record checks, and regain your freedom? (WhatsApp: +49 1521 5066462) (Email: wesbutman0(a)gmail.com) Our company has many years of experience in producing fake passports and other ID documents. We use high-quality equipment and materials to produce fake passports. We carefully replicate all the secret features of real passports to create fake documents. We are the best manufacturer of high-quality fake ID documents. (WhatsApp: +49 1521 5066462) (WeChat ID: Wesbutman) (Telegram: wesbutman0) (Email: wesbutman0(a)gmail.com) https://firstdocumentsonline.com/ http://buytraveldocsonline.com/

3 days, 15 hours

by foltzbutman＠gmail.com

3 days, 15 hours

Re: [PATCH v5 0/9] vfio/pci: Add mmap() for DMABUFs

by Matt Evans

Hi David, On 16/07/2026 22:23, David Matlack wrote: > On 2026-07-16 03:51 PM, Matt Evans wrote: >> Hi David, >> >> On 15/07/2026 19:12, David Matlack wrote: >>> On Wed, Jul 15, 2026 at 10:47 AM Matt Evans <matt(a)ozlabs.org> wrote: >>> >>>> This is based on v7.2-rc3. >>>> >>>> These commits are on GitHub for easier browsing, along with >>>> "[RFC ONLY] selftests: vfio: Add standalone vfio_dmabuf_mmap_test": >>>> >>>> https://github.com/metamev/linux/compare/v7.2-rc3...dev/mev/vfio-dmabuf-mma… >>> >>> It'd be great to have this test upstream. I'm happy to review it when >>> you're ready. Looks like it just needs to be redone to use the VFIO >>> selftests library and kselftests harness. AI could probably do the >>> conversion pretty quick :) >> >> For sure, I'd intended to catch up with you on best approach here. :) >> >> Aside from the organic structure of the test (the open-coded VFIO >> device/group setup/init needs to go), the main issue is that it relies >> on a hacked/out of tree QEMU "EDU++" device with a second larger BAR >> (containing freely read-writable memory). A subset of tests run with >> the in-tree EDU device, but coverage is too low. >> >> The desirable properties are: >> >> - Having a BAR that is pure memory (all locations present, writable >> without disruptive side-effects) so that mapping aliases can be >> constructed and detected. This is good to test things like non-zero >> vm_pgoffs and VA space presentation of physically-discontiguous DMABUFs. >> >> - BAR >> hugepage size so we can eyeball huge mappings work (or better, >> mechanically test for them). At least 32MB would tick this box for 4K, >> 16K page systems. >> >> - Something QEMU supports*, so one can run the test in a VM/TCG system. >> >> There were some real device models in QEMU that could be used this way, >> but needed a fair bit of setup; I didn't want to rathole >> vfio_dmabuf_mmap_test on including a ton of device-specific code for >> some video card or similar. >> >> I'll dig more for a simple target that provides these properties -- >> obviously it would be better to point this test at an off-the-shelf >> device (including silicon!). And, proposing EDU extensions to the QEMU >> folks may be useful (there're uses for a better EDU in other contexts too). >> >> Since this test uses MMIO for a specific [class of] function, my first >> thought is it should be another VFIO driver-type test sibling of >> vfio_pci_driver_test. For example, we could extend the driver-type >> tests' backend struct vfio_pci_driver_ops for functions capable of >> providing a Big Memory BAR, like QEMU EDU++. EDU can also memcpy, so >> could also support vfio_pci_driver_test. >> >> The spirit of the device backends hiding setup of a complex device is >> handy, and it's plausible that several backends could provide this "big >> memory BAR" service. What do you think, any concerns with extending >> vfio_pci_driver_ops like that? > > I wouldn't recommend leveraging the driver framework unless absolutely > necessary. It makes the test harder to run. > > The biggest issue I see with the proposed properties is being able to > treat the BAR as memory. That obviously will depend on the device and > may require device-specific setup. If we decide that treating the BAR as > memory is truly required then using the driver framework is the way to > go. But I'm hoping we can avoid that requirement. > > Instead, I think you can get pretty far by inspecting /proc/pid/pagemap > to determine if the mmap() set things up correctly, without actually > accessing the BAR. You can use /proc/pid/pagemap to look up the PFN and > PAGEMAP_SCAN to detect huge pages. Hmm, possible, although that's quite a different test at that point. I agree never touching the device has advantages, but it's harder to test certain things if we _never_ do MMIO. The mitigation effort to get coverage may not be the right tradeoff vs easier running. I can think of some "easy" VFIO bugs that would be challenging to properly verify in userspace (e.g. PFNs all having some undesired offset). The current test method is harder to fool per unit effort in writing it. Though, I will have a think about this no-touch flavour of test. What were you picturing regarding populating the VMA PTEs in order to inspect the result via /proc/pid/pagemap, whilst still upholding the principle of not touching the device? For example, madvise(MADV_POPULATE_WRITE) won't work on the VFIO BAR regions because they're VM_PFNMAP/VM_IO. > With that requirement gone, then all you really need is a device with a > large enough BAR. And even that it not a hard requirement. I'm sure > there are plenty of test cases that could work with smaller BARs. The > few tests that want to exercise huge mappings can inspect the device BAR > sizes first, and if they're all too small, SKIP() the test. > > If you structure the test this way, then it's easy for the test to be > used. It can be run against any device for the basic functional > coverage, and can be run against a device with a larger BAR for full > coverage of huge mappings. > > Does QEMU emulate any devices that have 32MB or larger BARs? Yep, looks like `-device pci-testdev,membar=64M,membar-backed=on` or even `-device bochs-display,vgamem=64M` would be suitable. So I'll also try moving the existing test over to one of these to at least remove the EDU++ device dependency. (bochs-display has >1 BAR, and some MMIO regs which are nice for a quick kick-the-tyres access test.) Cheers, Matt

3 days, 21 hours

A Beginner’s Guide to Enjoying Fnaf: Why This Horror Game Still Feels So Tense

by acute.hummingbird.ljmk＠hidepost.net

https://fivenightsatfreddysgame.io/ Introduction Horror games come in many forms. Some rely on monsters chasing you through dark hallways, while others create fear by making you feel trapped and helpless. One of the most famous examples of the second approach is Fnaf, short for Five Nights at Freddy’s. What makes the game interesting is that you don’t spend most of your time running around. Instead, you sit in a small security office, watching cameras and trying to survive until morning. The idea sounds simple at first, but the tension builds surprisingly fast. Every sound becomes suspicious, every camera check feels important, and every mistake can end the night immediately. For players who are new to horror games, Fnaf is a great example of how atmosphere and anticipation can be more frightening than constant action. Gameplay: What You Actually Do The basic setup is easy to understand. You play as a night security guard working at a family entertainment restaurant filled with animatronic characters. During the day they entertain guests, but at night they begin moving around the building. Your goal is straightforward: survive from midnight until 6 AM. To do that, you have a few tools: • Security cameras • Door controls • Hallway lights • Limited electrical power Most of the gameplay revolves around monitoring the cameras to track where the animatronics are located. If one gets too close to your office, you may need to close a door or check a hallway light. The problem is that every action consumes power, and once the power runs out, your defenses become much weaker. This creates the game’s main challenge: balancing information and resources. Check the cameras too often and you waste power. Ignore them for too long and an animatronic may reach your office without warning. That constant trade-off is what keeps the game tense even after you understand the rules. Why Fnaf Feels Different From Other Horror Games Many horror games focus on exploration, puzzles, or combat. Fnaf takes a much more restricted approach. You’re mostly sitting in one room. Surprisingly, that limitation makes the experience more intense. Because you can’t freely escape danger, you’re forced to pay attention to small details: • Footsteps • Mechanical noises • Camera movement • Sudden silence • Flickering lights The fear comes from anticipation rather than action. You know something is moving toward you, but you’re never completely sure when it will arrive. Another reason the game became so popular is its memorable characters. The animatronics are designed to look friendly on the surface, yet they become unsettling the longer you watch them. That contrast between a cheerful restaurant and a threatening nighttime atmosphere creates a unique style of horror. Tips for New Players If you’re trying Fnaf for the first time, the early nights can feel overwhelming. Here are a few simple tips that helped many players, including me, enjoy the game more. 1. Stay Calm The game is designed to make you panic. When something suddenly appears near your office, it’s easy to start clicking buttons randomly. Taking a breath and reacting carefully usually works better. 2. Learn the Camera Layout Spend a little time memorizing where the important rooms are located. Knowing which cameras connect to your office helps you react faster when animatronics begin moving. 3. Don’t Overuse the Doors A common beginner mistake is keeping the doors closed all the time. This drains power quickly. Use them only when an animatronic is actually nearby. 4. Listen Carefully Sound is extremely important. Headphones can make a big difference because audio cues often tell you more than the cameras do. 5. Expect a Few Jump Scares Everyone gets surprised at first. Instead of trying to avoid every jump scare, treat them as part of the learning process. After a few attempts, you’ll start recognizing the warning signs earlier. 6. Take Breaks if Needed Fnaf can be surprisingly stressful, especially during later nights. If your heart is racing after a tough attempt, there’s nothing wrong with taking a short break before trying again. The Best Way to Experience It In my opinion, Fnaf is most enjoyable when played in a quiet room with headphones and minimal distractions. The game relies heavily on atmosphere, so playing while multitasking removes much of the tension. I also recommend going into the game without watching too many strategy videos first. Discovering how the animatronics behave on your own makes the experience much more memorable. Part of the fun is slowly understanding the patterns and improving night by night. Playing with friends nearby can be entertaining too. Even people who aren’t controlling the game often react strongly to the sudden scares and close calls. Conclusion Fnaf remains one of the most recognizable horror games because it proves that a simple idea can create incredible tension. You don’t need complicated controls, huge maps, or constant combat to feel nervous. Sometimes sitting alone in a small office with limited power is enough. The game rewards observation, patience, and resource management while delivering plenty of suspense along the way. Whether you’re completely new to horror games or just looking for a classic experience, Fnaf offers a unique mix of strategy and fear that still holds up years later. If you decide to try it, don’t worry about surviving every night immediately. The fun comes from learning the patterns, reacting under pressure, and slowly becoming more confident as the nights get harder. That gradual progression is what makes the experience so memorable.

4 days, 4 hours

Re: [PATCH v5 0/9] vfio/pci: Add mmap() for DMABUFs

by David Laight

On Thu, 16 Jul 2026 21:23:22 +0000 David Matlack <dmatlack(a)google.com> wrote: > On 2026-07-16 03:51 PM, Matt Evans wrote: > > Hi David, > > > > On 15/07/2026 19:12, David Matlack wrote: > > > On Wed, Jul 15, 2026 at 10:47 AM Matt Evans <matt(a)ozlabs.org> wrote: > > > > > >> This is based on v7.2-rc3. > > >> > > >> These commits are on GitHub for easier browsing, along with > > >> "[RFC ONLY] selftests: vfio: Add standalone vfio_dmabuf_mmap_test": > > >> > > >> https://github.com/metamev/linux/compare/v7.2-rc3...dev/mev/vfio-dmabuf-mma… > > > > > > It'd be great to have this test upstream. I'm happy to review it when > > > you're ready. Looks like it just needs to be redone to use the VFIO > > > selftests library and kselftests harness. AI could probably do the > > > conversion pretty quick :) > > > > For sure, I'd intended to catch up with you on best approach here. :) > > > > Aside from the organic structure of the test (the open-coded VFIO > > device/group setup/init needs to go), the main issue is that it relies > > on a hacked/out of tree QEMU "EDU++" device with a second larger BAR > > (containing freely read-writable memory). A subset of tests run with > > the in-tree EDU device, but coverage is too low. > > > > The desirable properties are: > > > > - Having a BAR that is pure memory (all locations present, writable > > without disruptive side-effects) so that mapping aliases can be > > constructed and detected. This is good to test things like non-zero > > vm_pgoffs and VA space presentation of physically-discontiguous DMABUFs. > > > > - BAR >> hugepage size so we can eyeball huge mappings work (or better, > > mechanically test for them). At least 32MB would tick this box for 4K, > > 16K page systems. > > > > - Something QEMU supports*, so one can run the test in a VM/TCG system. > > > > There were some real device models in QEMU that could be used this way, > > but needed a fair bit of setup; I didn't want to rathole > > vfio_dmabuf_mmap_test on including a ton of device-specific code for > > some video card or similar. > > > > I'll dig more for a simple target that provides these properties -- > > obviously it would be better to point this test at an off-the-shelf > > device (including silicon!). And, proposing EDU extensions to the QEMU > > folks may be useful (there're uses for a better EDU in other contexts too). > > > > Since this test uses MMIO for a specific [class of] function, my first > > thought is it should be another VFIO driver-type test sibling of > > vfio_pci_driver_test. For example, we could extend the driver-type > > tests' backend struct vfio_pci_driver_ops for functions capable of > > providing a Big Memory BAR, like QEMU EDU++. EDU can also memcpy, so > > could also support vfio_pci_driver_test. > > > > The spirit of the device backends hiding setup of a complex device is > > handy, and it's plausible that several backends could provide this "big > > memory BAR" service. What do you think, any concerns with extending > > vfio_pci_driver_ops like that? > > I wouldn't recommend leveraging the driver framework unless absolutely > necessary. It makes the test harder to run. > > The biggest issue I see with the proposed properties is being able to > treat the BAR as memory. That obviously will depend on the device and > may require device-specific setup. If we decide that treating the BAR as > memory is truly required then using the driver framework is the way to > go. But I'm hoping we can avoid that requirement. Could you run a test where only a known part of the BAR can be treated as memory? A large BAR is likely to have some areas that can be accessed as memory. David > > Instead, I think you can get pretty far by inspecting /proc/pid/pagemap > to determine if the mmap() set things up correctly, without actually > accessing the BAR. You can use /proc/pid/pagemap to look up the PFN and > PAGEMAP_SCAN to detect huge pages. > > With that requirement gone, then all you really need is a device with a > large enough BAR. And even that it not a hard requirement. I'm sure > there are plenty of test cases that could work with smaller BARs. The > few tests that want to exercise huge mappings can inspect the device BAR > sizes first, and if they're all too small, SKIP() the test. > > If you structure the test this way, then it's easy for the test to be > used. It can be run against any device for the basic functional > coverage, and can be run against a device with a larger BAR for full > coverage of huge mappings. > > Does QEMU emulate any devices that have 32MB or larger BARs? >

4 days, 5 hours

[PATCH v5 0/9] vfio/pci: Add mmap() for DMABUFs

by Matt Evans

Hi all, The goal of this series is to enable userspace driver designs that use VFIO to export DMABUFs representing subsets of PCI device BARs, and "vend" those buffers from a primary process to other subordinate processes by fd. These processes then mmap() the buffers and their access to the device is isolated to the exported ranges. This is an improvement on sharing the VFIO device fd to subordinate processes, which would allow unfettered access. This is achieved by enabling mmap() of vfio-pci DMABUFs, passed by fd to subordinate processes. Second, a new revocation mechanism is added to allow the primary process to forcibly revoke access to previously-shared BAR spans, even if the subordinate processes haven't cleanly exited. (The related topic of safe delegation of iommufd control to the subordinate processes is not addressed here, and is follow-up work.) The background/rationale is covered in more detail in the RFC cover letters. Feedback from the RFCs requested that, instead of creating DMABUF-specific vm_ops and .fault paths, to go the whole way and migrate the existing VFIO PCI BAR mmap() to be backed by a DMABUF too, resulting in a common vm_ops and fault handler for mmap()s of both the VFIO device and explicitly-exported DMABUFs. This will help future iommufd emulation of VFIO Type1 peer-to-peer, making it easier to get a DMABUF for a VFIO BAR as a DMA target. mmap() conversion to use DMABUF underneath has been done for vfio-pci, but not sub-drivers: nvgrace-gpu's mmap() override path is unchanged; I kept this out of scope for now not least because I don't have a thorough test setup for this system. I would prefer to help the nvgrace-gpu maintainers enable BAR mmap() DMABUFs themselves. Notes on patches ================ PCI/P2PDMA: Split pool-related cleanup out of pci_p2pdma_release() PCI/P2PDMA: Add CONFIG_PCI_P2PDMA_CORE Later in the series, vfio-pci's mmap() is going to depend on pcim_p2pdma_provider() which depended on CONFIG_PCI_P2PDMA, which in turn depended on ZONE_DEVICE. That isn't available on 32-bit and some archs, because they lack MEMORY_HOTPLUG and friends. VFIO does _not_ require actual P2P to be present for basic mmap() functionality, only for the optional CONFIG_DMA_SHARED_BUFFER feature. These split out p2pdma_core.c under CONFIG_PCI_P2PDMA_CORE (which currently contains pcim_p2pdma_provider()), and an optional CONFIG_PCI_P2PDMA which depends on ZONE_DEVICE etc. providing P2P functionality in the existing p2pdma.c. The first splits out pool cleanup from the release path, and the second does the refactor/code move to the new file. vfio/pci: Add a helper to look up PFNs for DMABUFs vfio/pci: Add a helper to create a DMABUF for a BAR-map VMA The first adds a DMABUF VMA fault handler helper to determine arbitrary-sized PFNs from ranges in DMABUF. The second refactors DMABUF export for use by the existing export feature, and adds a helper that creates a DMABUF corresponding to a VFIO BAR mmap() request. vfio/pci: Convert BAR mmap() to use a DMABUF The vfio-pci core mmap() creates a DMABUF with the helper above, and the vm_ops fault handler uses the other helper to resolve the fault. Because this depends on DMABUF structs/code, CONFIG_VFIO_PCI_CORE needs to depend on CONFIG_DMA_SHARED_BUFFER. The CONFIG_VFIO_PCI_DMABUF still conditionally enables the export support code. NOTE: The user mmap()s a device fd, but the resulting VMA's vm_file becomes that of the DMABUF. The DMABUF takes ownership of the device file and put()s it on release, which maintains the existing behaviour of a VMA keeping the VFIO device open. BAR zapping then happens via the existing vfio_pci_dma_buf_move() path, which now needs to unmap PTEs in the DMABUF's address_space. vfio/pci: Provide a user-facing name for BAR mappings There was a request for decent debug naming in /proc/<pid>/maps etc. comparable to the existing VFIO names: since the VMAs are DMABUFs, they have a "dmabuf:" prefix and can't be 100% identical to before. This is a user-visible change, but this patch at least now gives us extra info on the BDF & BAR being mapped. vfio/pci: Clean up BAR zap and revocation In general (see NOTE!) the vfio_pci_zap_bars() is now obsolete, since it unmaps PTEs in the VFIO device address_space which is now unused. This consolidates all calls (e.g. around reset) with the neighbouring vfio_pci_dma_buf_move()s into new functions, to revoke/unrevoke (making the steps clearer). NOTE: Because drivers can use their own vm_ops and override .mmap, the core must conservatively assume an overridden .mmap might still add PTEs to the VFIO device address_space and therefore still does the zap. A new flag, zap_bars_on_revoke, enables the zap when .mmap is overridden. A driver that does not need the zap can clear this to opt-out, e.g. if the driver calls down to the common mmap (and so uses DMABUFs). hisi-acc-vfio-pci does just this, and thus sets the opt-out flag. vfio/pci: Support mmap() of a VFIO DMABUF Adds mmap() for a DMABUF fd exported from vfio-pci. It was a goal to keep the VFIO device fd lifetime behaviour unchanged with respect to the DMABUFs. An application can close all device fds, and this will revoke/clean up all DMABUFs; then, no mappings or other access can be performed. When enabling mmap() of the DMABUFs, this means access through the VMA is also revoked. This complicates the fault handler because whilst the DMABUF exists, it has no guarantee that the corresponding VFIO device is still alive. Adds synchronisation ensuring the vdev is available before vdev->memory_lock is touched; this holds the device registration so that even if the buffer has been cleaned up, vdev hasn't been freed and so the lock can be safely taken. vfio/pci: Permanently revoke a DMABUF on request This is mostly a rename of `revoked` to an enum, `status`, and adding a third state for a buffer: usable, revoked temporary, revoked permanent. A new VFIO feature is added, VFIO_DEVICE_FEATURE_DMA_BUF_REVOKE, which takes a DMABUF (exported from the same device) and permanently revokes it. Thus a userspace driver can guarantee any downstream consumers of a shared fd are prevented from accessing a BAR range, and that range can be reused. NOTE: This might block userspace, waiting on importers to detach. The code doing revocation in vfio_pci_dma_buf_move() is moved, to a common function for use by ..._move() and this new feature. NOTE: See changelog, by request v4 added a condition to the existing code to elide the unnecessary invalidation/sync on the un-revoke path.) NOTE: Previous versions contained an additional feature patch, "vfio/pci: Add mmap() attributes to DMABUF feature". This has been dropped in v5 because: - The mechanism simply set vma->vm_page_prot. This would be sufficient for arm64 and other architectures. - However, (locally-run claude-opus-4-8) Sashiko flagged that, on x86, additional memtype handling is required to set up the PAT. Without this, the memtype is returned back to UC- by pfnmap_setup_cachemode() upon PTE creation. Most other sources of userspace WC mappings create PTEs eagerly with e.g. io_remap_pfn_range() which memtype_reserve() WC for the range. Getting them with lazy-fault used by vfio-pci is more complicated (e.g. perhaps registering WC for BARs with PAT/MTRRs, and deciding how to deal with aliasing...). Since this feature is not critical for this series to be useful, I've decided for now to drop it in favour of a simpler series now and revisiting this separ*ately. Testing ======= (The [RFC ONLY] userspace test program, for QEMU edu-plus, can be found in the GitHub branch below. It at least illustrates how the export, map, revoke, and close semantics interoperate.) This code has been tested in mapping DMABUFs of single/multiple ranges from multiple BARs, aliasing mmap()s, aliasing ranges across DMABUFs, vm_pgoff > 0, revocation, shutdown/cleanup scenarios, and hugepage mappings. No regressions observed on the VFIO selftests, or on our internal vfio-pci applications. VFIO on i386 has been build-tested. Dear Reviewers, =============== I was grateful for the reviews and Reviewed-Bys on previous versions. Thanks; I've added some Reviewed-Bys/Acks. I have NOT included your tags where the patch has materially changed after your review (or where requested changes ended up more than super-trivial). I hope that's okay. End === This is based on v7.2-rc3. These commits are on GitHub for easier browsing, along with "[RFC ONLY] selftests: vfio: Add standalone vfio_dmabuf_mmap_test": https://github.com/metamev/linux/compare/v7.2-rc3...dev/mev/vfio-dmabuf-mma… Thanks for reading, Matt ================================================================================ Changelog: v5: - Rebased on 7.2-rc3 - Dropped the memattr/WC feature (see explanation above). - "vfio/pci: Convert BAR mmap() to use a DMABUF": Fixed a potentially-nasty bug (which (locally-run) Sashiko found!) whereby the unmap_mapping_range() performed in cleanup was passed a range up from offset zero for the DMABUF size. Initially this was how all DMABUFs were created and an appropriate zap, but a new version kept the VFIO region index encoded in the offset -- for BAR > 0 the unmap span would then mismatch. Instead, pass size 0 to mean an "all" range. Because the goal is to shoot down everything relating to one DMABUF and the address_space can only contain things relating to that DMABUF, this is equivalent and has the bonus of never failing to match mappings... Praan, Kevin, I kept your R-Bs on this fix. - The revoke patch converts vfio_pci_dma_buf_cleanup()'s priv->vdev = NULL to a WRITE_ONCE, corresponding to the revoke function's READ_ONCE (performed to test that the VFIO and DMABUF are related). - Clarified the VFIO_DEVICE_FEATURE_DMA_BUF_REVOKE UAPI comments, documenting previously-missing error cases and their reasons. v4: https://lore.kernel.org/all/20260701171245.90111-1-matt@ozlabs.org/ v3: https://lore.kernel.org/all/20260610154327.37758-1-matt@ozlabs.org/ v2: https://lore.kernel.org/all/20260527102319.100128-1-mattev@meta.com/ v1: https://lore.kernel.org/kvm/20260416131815.2729131-1-mattev@meta.com/ RFCv2: https://lore.kernel.org/kvm/20260312184613.3710705-1-mattev@meta.com/ RFCv1: https://lore.kernel.org/all/20260226202211.929005-1-mattev@meta.com/ Tech topic: https://lore.kernel.org/linux-iommu/20250918214425.2677057-1-amastro@fb.com/ Matt Evans (9): PCI/P2PDMA: Split pool-related cleanup out of pci_p2pdma_release() PCI/P2PDMA: Add CONFIG_PCI_P2PDMA_CORE vfio/pci: Add a helper to look up PFNs for DMABUFs vfio/pci: Add a helper to create a DMABUF for a BAR-map VMA vfio/pci: Convert BAR mmap() to use a DMABUF vfio/pci: Provide a user-facing name for BAR mappings vfio/pci: Clean up BAR zap and revocation vfio/pci: Support mmap() of a VFIO DMABUF vfio/pci: Permanently revoke a DMABUF on request MAINTAINERS | 2 +- drivers/pci/Kconfig | 5 + drivers/pci/Makefile | 1 + drivers/pci/p2pdma.c | 113 +--- drivers/pci/p2pdma.h | 29 + drivers/pci/p2pdma_core.c | 122 +++++ drivers/vfio/pci/Kconfig | 5 +- drivers/vfio/pci/Makefile | 3 +- .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 8 + drivers/vfio/pci/vfio_pci_config.c | 30 +- drivers/vfio/pci/vfio_pci_core.c | 210 +++++-- drivers/vfio/pci/vfio_pci_dmabuf.c | 515 +++++++++++++++--- drivers/vfio/pci/vfio_pci_priv.h | 53 +- include/linux/pci-p2pdma.h | 24 +- include/linux/pci.h | 2 +- include/linux/vfio_pci_core.h | 1 + include/uapi/linux/vfio.h | 25 + 17 files changed, 875 insertions(+), 273 deletions(-) create mode 100644 drivers/pci/p2pdma.h create mode 100644 drivers/pci/p2pdma_core.c -- 2.50.1 (Apple Git-155)

4 days, 6 hours

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig