Re: [PATCH 6/10] lguest code: the little linux hypervisor.

> Yes, it is a bit, umm, innovative.  If it is going to be kept, even if 
> just for devel logging, you should disable interrupts around it.  
> Changing segments is not a normal thing to do.

Actually that wouldn't be needed because interrupts are not allowed to do any 
user accesses. And contrary to the name it doesn't actually change
the segment registers, only state used by *_user.

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

---

• Follow-Ups:
  • Re: [PATCH 6/10] lguest code: the little linux hypervisor.
    • From: David Miller <[email protected]>
  • Re: [PATCH 6/10] lguest code: the little linux hypervisor.
    • From: Zachary Amsden <[email protected]>

• References:
  • [PATCH 0/10] lguest
    • From: Rusty Russell <[email protected]>
  • Re: [PATCH 6/10] lguest code: the little linux hypervisor.
    • From: Rusty Russell <[email protected]>
  • Re: [PATCH 6/10] lguest code: the little linux hypervisor.
    • From: Zachary Amsden <[email protected]>

• Prev by Date: Re: [rfc][patch 0/3] a faster buffered write deadlock fix?
• Next by Date: Re: [PATCH 1/10] lguest: Don't rely on last-linked fallthru when no paravirt handler
• Previous by thread: Re: [PATCH 6/10] lguest code: the little linux hypervisor.
• Next by thread: Re: [PATCH 6/10] lguest code: the little linux hypervisor.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]