- User Since
- Jun 4 2014, 6:42 AM (414 w, 4 d)
Feb 17 2022
Feb 16 2022
Feb 9 2022
Feb 8 2022
Feb 4 2022
Feb 2 2022
Feb 1 2022
@imp , I am not sure if we are disagreeing about anything.
I just explained why the current code the way it is (for shared interrupts).
And stated that the non-shared interrupts case is different.
Jan 31 2022
Yes, rid 0 is for legacy PCI interrupts and rids >= 1 are for MSI / MSI-X.
So, indeed, a proper barrier would require iterating over all active interrupt resources.
Jan 30 2022
Jan 27 2022
Jan 26 2022
I am a bit torn on this.
On the one hand, I like the simplicity that comes from returning errno codes to userland.
On the other hand, recently I had to write a program that had to use "low level" ioctl-s like I2CSTART and I needed to be able to distinguish IIC_ENOACK from other bus conditions.
In any case, the current state of matters where a return value can be either an errno code or an IIC code is clearly a mess.
Jan 25 2022
Jan 22 2022
Jan 21 2022
Jan 19 2022
Jan 12 2022
Jan 11 2022
address comments from mav
@manu , not sure if this is the approach that you had in mind.
But I think it's better to discuss based on some concrete code rather than abstractly.
At work we have an extension that allows to dump (and save) both a text dump and a vmcore at the same time.
We use that to easily capture from ddb things that are hard (but not impossible) to get with kgdb.
The path you open here is a great alternative to that.
Jan 8 2022
LGTM. My only comment is that I am not sure if the file really has any sorting order, but there is some resemblance of it, so maybe it's worthwhile keeping it.
Jan 3 2022
Dec 29 2021
Does it test things like setting bufsize to a significant portion of total memory?
Might be worthwhile testing that directly.
Dec 27 2021
Dec 26 2021
Dec 25 2021
Dec 24 2021
Thank you, Toomas.
Could you please run this change by illumos folks as well?
It seems that my emails to email@example.com are not reaching the list.