Re: Some interesting observations when trying to optimize vmstat handling

Andi Kleen wrote:
> The only problem is that there might be some code who relies on 
> restore_flags() restoring other flags that IF, but at least for interrupts
> and local_irq_save/restore it should be fine to change.
>   

I don't think so.  We don't bother to save/restore the other flags in
Xen paravirt and it doesn't seem to cause a problem.  The semantics
really are specific to the state of the interrupt flag.

    J
-
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: Some interesting observations when trying to optimize vmstat handling
    • From: Andi Kleen <[email protected]>

• References:
  • Some interesting observations when trying to optimize vmstat handling
    • From: Christoph Lameter <[email protected]>
  • Re: Some interesting observations when trying to optimize vmstat handling
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: oops in oprofile/dump_trace/X86 with 2.6.24-rcX
• Next by Date: Re: [poll] Is the megafreeze development model broken?
• Previous by thread: Re: Some interesting observations when trying to optimize vmstat handling
• Next by thread: Re: Some interesting observations when trying to optimize vmstat handling
• 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]