On Fri, May 18, 2018 at 07:18:57PM +0200, Paolo Bonzini wrote: > On 18/05/2018 19:13, Eduardo Habkost wrote: > >> As much as we'd like to be helpful and validate input, you need a real > >> time host too. I'm not sure how we'd find out - I suggest we do not > >> bother for now. > > I'm worried that people will start enabling the flag in all kinds > > of scenarios where the guarantees can't be kept, and make the > > meaning of the flag in practice completely different from its > > documented meaning. > > I don't think we should try to detect anything. As far as QEMU is > concerned, it's mostly garbage in, garbage out when it comes to invalid > configurations. It's just a bit, and using it in invalid configurations > is okay if you're doing it (for example) for debugging. In this case, I'd like the requirements and recommendations to be included in QEMU documentation. Especially to point out the most obvious and more likely mistakes (like not ensuring memory is pinned at all, or letting the vCPU threads be interrupted). So, is there a known list of steps required to configure a host to enable kvm-hints-realtime safely, already? I'd like the documentation to be better than "you should fiddle with the CPU affinity on your system and also ensure memory will be pinned; good luck". -- Eduardo -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
