lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 1 Nov 2006 13:03:32 -0800
From:	"David Schwartz" <davids@...master.com>
To:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: RE: How does the kernel interrupt a user process with code while (1) {}?


> Thanks.
>
> On 11/1/06, Jan Engelhardt <jengelh@...ux01.gwdg.de> wrote:
> > >
> > > As title, thanks ;-)
> >
> > Timer interrupt.

Other interrupts too. For example, if a disk I/O operation completes (or a
network packet is received) and generates an interrupt, the kernel could use
that interrupt to switch to another process made ready-to-run by the disk
operation or data received over the network.

Any interrupt can interrupt a user process.

DS


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ