ext2: How do we make sure indirect blocks are writeback before data block?

to dirty, and then the inode's associated block dev will write back this dirty buffer head. My question is these indirect blocks are meta data of this inode, and usually we should write back inode's data first and then its meta data, but here, after we mark buffer heads of indirect blocks and how do

Re: [QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi Namhyung :) On 07/05/2017 03:07 PM, Namhyung Kim wrote: Hi Taeung, On Wed, Jul 5, 2017 at 2:47 PM, Taeung Song wrote: Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a

Re: [QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi Namhyung :) On 07/05/2017 03:07 PM, Namhyung Kim wrote: Hi Taeung, On Wed, Jul 5, 2017 at 2:47 PM, Taeung Song wrote: Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a '--show-total-period' option and a 't' key

Re: [QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi Taeung, On Wed, Jul 5, 2017 at 2:47 PM, Taeung Song wrote: > Hi, > > Two problems of perf-annotate were mentioned in recent PATCH reviews > by Milian and Namhyung. > > Currently perf-annotate has a '--show-total-period' option > and a 't' key "Toggle total period

Re: [QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi Taeung, On Wed, Jul 5, 2017 at 2:47 PM, Taeung Song wrote: > Hi, > > Two problems of perf-annotate were mentioned in recent PATCH reviews > by Milian and Namhyung. > > Currently perf-annotate has a '--show-total-period' option > and a 't' key "Toggle total period view" on TUI browser. Hmm...

[QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a '--show-total-period' option and a 't' key "Toggle total period view" on TUI browser. However, they actually show the number of samples, not period(Raw number of

[QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a '--show-total-period' option and a 't' key "Toggle total period view" on TUI browser. However, they actually show the number of samples, not period(Raw number of

how do we

Hi all, Is Linux having 'non-break interface for serial console' ? I am currently using Kernel 2.6.7. how do we know this feature? Thanks Seetharam __ Yahoo! India Answers: Share what you know. Learn something new

how do we

Hi all, Is Linux having 'non-break interface for serial console' ? I am currently using Kernel 2.6.7. how do we know this feature? Thanks Seetharam __ Yahoo! India Answers: Share what you know. Learn something new

How do we handle multi-function devices? [was Re: [patch] ucb1x00: touchscreen cleanups]

--- Richard Purdie <[EMAIL PROTECTED]> wrote: > On Sun, 2005-07-31 at 23:11 +0100, Mark Underwood > wrote: > > As this isn't the only chip of this sort (i.e. a > > multi-function chip not on the CPU bus) maybe we > > should store the bus driver in a common place. If > > needed we could have a

How do we handle multi-function devices? [was Re: [patch] ucb1x00: touchscreen cleanups]

--- Richard Purdie [EMAIL PROTECTED] wrote: On Sun, 2005-07-31 at 23:11 +0100, Mark Underwood wrote: As this isn't the only chip of this sort (i.e. a multi-function chip not on the CPU bus) maybe we should store the bus driver in a common place. If needed we could have a very simple

Re: [KBUILD] How do we handle autoconfiguration?

Giacomo A. Catenazzi <[EMAIL PROTECTED]>: > I've difficult to merge with the CML1/2: > > In CML2-0.8.3 the include frozen flag (-I) is broken, and > also the new -W flag is broken, thus no real test. 0.9.0 fixes the -W flag. I wasn't able to reproduce your problem with -I. --

Re: [KBUILD] How do we handle autoconfiguration?

"Eric S. Raymond" wrote: > > I backed away from this because Giacomo Catenazzi told me he was > working on a separate autoconfigurator that would generate config > files in CML1 format. That's a cleaner design -- one would run his > autoconfigurator and then import the resulting config into the

Re: How do we handle autoconfiguration?

[CC: list drastically trimmed] [EMAIL PROTECTED] (Eric S. Raymond) wrote on 26.12.00 in <[EMAIL PROTECTED]>: > Linus, replying to Alan: > >> If we do that I'd rather see a make autoconfig that does the lot from > >> proc/pci etc 8) > > > >Good point. No point in adding a new config option, we

Re: [KBUILD] How do we handle autoconfiguration?

"Eric S. Raymond" wrote: > > I wrote: > >Giacomo, what's the state of your project? > > Sigh, I got an address-invalid bounce from Giacomo. Looks like he > may have fallen off the net. I still receive mails! Maybe try [EMAIL PROTECTED] [better administrators, better software :-)]

Re: [KBUILD] How do we handle autoconfiguration?

"Eric S. Raymond" wrote: I wrote: Giacomo, what's the state of your project? Sigh, I got an address-invalid bounce from Giacomo. Looks like he may have fallen off the net. I still receive mails! Maybe try [EMAIL PROTECTED] [better administrators, better software :-)] giacomo -

Re: How do we handle autoconfiguration?

[CC: list drastically trimmed] [EMAIL PROTECTED] (Eric S. Raymond) wrote on 26.12.00 in [EMAIL PROTECTED]: Linus, replying to Alan: If we do that I'd rather see a make autoconfig that does the lot from proc/pci etc 8) Good point. No point in adding a new config option, we should just

Re: [KBUILD] How do we handle autoconfiguration?

"Eric S. Raymond" wrote: I backed away from this because Giacomo Catenazzi told me he was working on a separate autoconfigurator that would generate config files in CML1 format. That's a cleaner design -- one would run his autoconfigurator and then import the resulting config into the CML2

Re: [KBUILD] How do we handle autoconfiguration?

Giacomo A. Catenazzi [EMAIL PROTECTED]: I've difficult to merge with the CML1/2: In CML2-0.8.3 the include frozen flag (-I) is broken, and also the new -W flag is broken, thus no real test. 0.9.0 fixes the -W flag. I wasn't able to reproduce your problem with -I. -- a

Re: [KBUILD] How do we handle autoconfiguration?

esr> # PROCESSOR is string valued; we capture stdout from the probe esr> derive PROCESSOR from "myprobe1.sh" esr> esr> # FOOFEATURE is boolean; we look at the return status from myprobe2.py esr> derive FOOFEATURE from "myprobe2.py" I think this is cool. esr> (kbuild people, this is one reason

How do we handle autoconfiguration?

I wrote: >Giacomo, what's the state of your project? Sigh, I got an address-invalid bounce from Giacomo. Looks like he may have fallen off the net. -- >>esr>> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

How do we handle autoconfiguration?

Linus, replying to Alan: >> If we do that I'd rather see a make autoconfig that does the lot from >> proc/pci etc 8) > >Good point. No point in adding a new config option, we should just have a >new configurator instead. Of course, it can't handle many of the >questions, so it would still have to

How do we handle autoconfiguration?

Linus, replying to Alan: If we do that I'd rather see a make autoconfig that does the lot from proc/pci etc 8) Good point. No point in adding a new config option, we should just have a new configurator instead. Of course, it can't handle many of the questions, so it would still have to fall

How do we handle autoconfiguration?

I wrote: Giacomo, what's the state of your project? Sigh, I got an address-invalid bounce from Giacomo. Looks like he may have fallen off the net. -- esr - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: [KBUILD] How do we handle autoconfiguration?

esr # PROCESSOR is string valued; we capture stdout from the probe esr derive PROCESSOR from "myprobe1.sh" esr esr # FOOFEATURE is boolean; we look at the return status from myprobe2.py esr derive FOOFEATURE from "myprobe2.py" I think this is cool. esr (kbuild people, this is one reason I