Hi,
Quoting Robert Millan (2016-03-05 11:20:35)
> El 28/02/16 a les 00:33, Justus Winter ha escrit:
> > This requires a tiny change to libddekit. I'll send it as a
> > follow-up. With it libddekit supports both the new and old kind of
> > notification to make upgrades painless.
>
> This sounds
Hi Justus
El 28/02/16 a les 00:33, Justus Winter ha escrit:
> This requires a tiny change to libddekit. I'll send it as a
> follow-up. With it libddekit supports both the new and old kind of
> notification to make upgrades painless.
This sounds like it could affect the implementation in Rump,
Justus Winter, on Sun 28 Feb 2016 23:51:40 +0100, wrote:
> Quoting Samuel Thibault (2016-02-28 22:35:14)
> > Justus Winter, on Sun 28 Feb 2016 00:33:20 +0100, wrote:
> > > 3/ ... instead the notification message carries a send right as the
> > > reply port, and the userspace server acknowledges the
Quoting Samuel Thibault (2016-02-28 22:35:14)
> Justus Winter, on Sun 28 Feb 2016 00:33:20 +0100, wrote:
> > 3/ ... instead the notification message carries a send right as the
> > reply port, and the userspace server acknowledges the interrupt by
> > deallocating this right.
>
> That makes much m
Justus Winter, on Sun 28 Feb 2016 00:33:20 +0100, wrote:
> 3/ ... instead the notification message carries a send right as the
> reply port, and the userspace server acknowledges the interrupt by
> deallocating this right.
That makes much more sense to me than the current disable/enable. I
guess
Hello,
I revised the patch that is delegating interrupts to userspace.
Notable changes:
1/ We now use proper dead-name notifications to detect that the send
right we use to send notifications goes stale, i.e. the userspace
server dies.
2/ 'device_intr_enable' is a nop now...
3/ ... instead the
