On Sun, Nov 13, 2022 at 09:01:32AM -0800, Ashok Raj wrote: > If it's Ok to ask a question. "You" above is the kernel? Of course the kernel. If you think about it, it makes sense only for the kernel to do any checking. As it is enforcing that only the proper blobs are loaded. Just like microcode. Userspace is only doing the triggering of the actions. > Microcode has no such functionality today right? User space > never inputs a filename, only performs echo 1 > reload. Yes, because it is as user-friendly as possible. Users should not care about filenames. But microcode needs only a single file. If you have multiple files like IFS, you could just as well supply them and the kernel would check every aspect before loading them. > If a file name composed by the kernel exists, then it checks the header > validity before proceeding. Yes. > So some of the files will work, some will fail, and user space doesn't > care? See my reply to Jithu: https://lore.kernel.org/r/Y3EiKUzpShqwzEf6@xxxxxxx > You are reviewing the code and I'm simply discussing what each person > means. I hope its OK to have a dialog. I say | Late loading works also trivially: | | echo 1 > /sys/devices/system/cpu/microcode/reload | | And it goes and builds the filename from f/m/s and loads it from the | hardcoded path - no filename resolving. | | But it doesn't ask the user to give a f/m/s or a sequence number. You reply with | I don't think the current proposed interface expects a f/m/s. The | entire IFS design was sort of mimicking the microcode interface." | | and you go on to explain what it used to do. I read what it used to do. So how does your reply have any relevance to what I'm saying? I go and give the full spiel on how it is important to support command line loading and how you don't really need a special tool, you say |The utility is more like icing, to run a simple test all you need is a |simple script. It is not a baseline requirement." which feels like you didn't read this part *at* *all*: | A special tool is *always* a burden. You need to build it, supply | it, make sure it is installable on the target system and so on. | | And I'm telling you this with my Linux distributor hat on. It is always | a pain - trust me. | | For example, there's a reason why you can still control ftrace from the | command line and you don't need any tool. You *can* use a tool but you | don't have to. IOW, the KISS philosophy. So now I ended up pasting practically the most of my text again. Why? Because your reply doesn't give me *any* signs that you actually read what I said. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
