* [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload @ 2019-04-04 16:57 Amir Goldstein 2019-04-04 21:17 ` Dave Chinner 2019-04-08 9:14 ` [xfs] fa3fe73bed: aim7.jobs-per-min -10.9% regression kernel test robot 0 siblings, 2 replies; 41+ messages in thread From: Amir Goldstein @ 2019-04-04 16:57 UTC (permalink / raw) To: Dave Chinner Cc: Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel This patch improves performance of mixed random rw workload on xfs without relaxing the atomic buffered read/write guaranty that xfs has always provided. We achieve that by calling generic_file_read_iter() twice. Once with a discard iterator to warm up page cache before taking the shared ilock and once again under shared ilock. Since this is a POC patch it also includes a separate fix to the copy_page_to_iter() helper when called with discard iterator. There is no other caller in the kernel to this method with a discard iterator as far as I could see. Signed-off-by: Amir Goldstein <amir73il@gmail.com> --- Hi Folks, With this experimenital patch I was able to bring performance of random rw workload benchmark on xfs much closer to ext4. Ext4, as most Linux filesystems doesn't take the shared inode lock on buffered reads and does not provide atomic buffered reads w.r.t buffered writes. Following are the numbers I got with filebench randomrw workload [1] on a VM with 4 CPUs and spindles. Note that this improvement is unrelated to the rw_semaphore starvation issue that was observed when running the same benchmark on fast SDD drive [2]. === random read/write - cold page cache === --- EXT4 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.1.0-rc2, ext4 rand-write1 862304ops 14235ops/s 111.2mb/s 0.5ms/op rand-read1 22065ops 364ops/s 2.8mb/s 21.5ms/op --- XFS --- filebench randomrw (8 read threads, 8 write threads) kernel 5.1.0-rc2, xfs rand-write1 39451ops 657ops/s 5.1mb/s 12.0ms/op rand-read1 2035ops 34ops/s 0.3mb/s 232.7ms/op --- XFS+ --- filebench randomrw (8 read threads, 8 write threads) kernel 5.1.0-rc2+ (xfs page cache warmup patch) rand-write1 935597ops 15592ops/s 121.8mb/s 0.5ms/op rand-read1 4446ops 74ops/s 0.6mb/s 107.6ms/op To measure the effects of two passes of generic_file_read_iter(), I ran a random read [2] benchmark on 5GB file with warm and cold page cache. === random read - cold page cache === --- EXT4 --- filebench randomread (8 read threads) - cold page cache kernel 5.1.0-rc2 rand-read1 23589ops 393ops/s 3.1mb/s 20.3ms/op --- XFS --- filebench randomread (8 read threads) - cold page cache kernel 5.1.0-rc2 rand-read1 20578ops 343ops/s 2.7mb/s 23.3ms/op --- XFS+ --- filebench randomread (8 read threads) - cold page cache kernel 5.1.0-rc2+ (xfs page cache warmup patch) rand-read1 20476ops 341ops/s 2.7mb/s 23.4ms/op === random read - warm page cache === --- EXT4 --- filebench randomread (8 read threads) - warm page cache kernel 5.1.0-rc2 rand-read1 58168696ops 969410ops/s 7573.5mb/s 0.0ms/op --- XFS --- filebench randomread (8 read threads) - warm page cache kernel 5.1.0-rc2 rand-read1 52748818ops 878951ops/s 6866.8mb/s 0.0ms/op --- XFS+ --- filebench randomread (8 read threads) - warm page cache kernel 5.1.0-rc2+ (xfs page cache warmup patch) rand-read1 52770537ops 879445ops/s 6870.7mb/s 0.0ms/op The numbers of this benchmark do not show and measurable difference for readers only workload with either cold or warm page cache. If needed I can provide more measurments with fio or with different workloads and different drives. Fire away! Thanks, Amir. [1] https://github.com/amir73il/filebench/blob/overlayfs-devel/workloads/randomrw.f [2] https://marc.info/?l=linux-xfs&m=155347265016053&w=2 [3] https://github.com/amir73il/filebench/blob/overlayfs-devel/workloads/randomread.f fs/xfs/xfs_file.c | 14 ++++++++++++++ lib/iov_iter.c | 5 +++-- 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c index 1f2e284..4e5f88a 100644 --- a/fs/xfs/xfs_file.c +++ b/fs/xfs/xfs_file.c @@ -240,6 +240,20 @@ xfs_file_buffered_aio_read( if (!xfs_ilock_nowait(ip, XFS_IOLOCK_SHARED)) return -EAGAIN; } else { + /* + * Warm up page cache to minimize time spent under + * shared ilock. + */ + struct iov_iter iter; + loff_t pos = iocb->ki_pos; + + iov_iter_discard(&iter, READ, iov_iter_count(to)); + ret = generic_file_read_iter(iocb, &iter); + if (ret <= 0) + return ret; + + iocb->ki_pos = pos; + xfs_ilock(ip, XFS_IOLOCK_SHARED); } ret = generic_file_read_iter(iocb, to); diff --git a/lib/iov_iter.c b/lib/iov_iter.c index ea36dc3..b22e433 100644 --- a/lib/iov_iter.c +++ b/lib/iov_iter.c @@ -893,9 +893,10 @@ size_t copy_page_to_iter(struct page *page, size_t offset, size_t bytes, size_t wanted = copy_to_iter(kaddr + offset, bytes, i); kunmap_atomic(kaddr); return wanted; - } else if (unlikely(iov_iter_is_discard(i))) + } else if (unlikely(iov_iter_is_discard(i))) { + i->count -= bytes; return bytes; - else if (likely(!iov_iter_is_pipe(i))) + } else if (likely(!iov_iter_is_pipe(i))) return copy_page_to_iter_iovec(page, offset, bytes, i); else return copy_page_to_iter_pipe(page, offset, bytes, i); -- 2.7.4 ^ permalink raw reply related [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-04 16:57 [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload Amir Goldstein @ 2019-04-04 21:17 ` Dave Chinner 2019-04-05 14:02 ` Amir Goldstein 2019-04-08 10:33 ` Jan Kara 2019-04-08 9:14 ` [xfs] fa3fe73bed: aim7.jobs-per-min -10.9% regression kernel test robot 1 sibling, 2 replies; 41+ messages in thread From: Dave Chinner @ 2019-04-04 21:17 UTC (permalink / raw) To: Amir Goldstein Cc: Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > This patch improves performance of mixed random rw workload > on xfs without relaxing the atomic buffered read/write guaranty > that xfs has always provided. > > We achieve that by calling generic_file_read_iter() twice. > Once with a discard iterator to warm up page cache before taking > the shared ilock and once again under shared ilock. This will race with thing like truncate, hole punching, etc that serialise IO and invalidate the page cache for data integrity reasons under the IOLOCK. These rely on there being no IO to the inode in progress at all to work correctly, which this patch violates. IOWs, while this is fast, it is not safe and so not a viable approach to solving the problem. FYI, I'm working on a range lock implementation that should both solve the performance issue and the reader starvation issue at the same time by allowing concurrent buffered reads and writes to different file ranges. IO range locks will allow proper exclusion for other extent manipulation operations like fallocate and truncate, and eventually even allow truncate, hole punch, file extension, etc to run concurrently with other non-overlapping IO. They solve more than just the performance issue you are seeing.... Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-04 21:17 ` Dave Chinner @ 2019-04-05 14:02 ` Amir Goldstein 2019-04-07 23:27 ` Dave Chinner 2019-04-08 10:33 ` Jan Kara 1 sibling, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2019-04-05 14:02 UTC (permalink / raw) To: Dave Chinner Cc: Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > This patch improves performance of mixed random rw workload > > on xfs without relaxing the atomic buffered read/write guaranty > > that xfs has always provided. > > > > We achieve that by calling generic_file_read_iter() twice. > > Once with a discard iterator to warm up page cache before taking > > the shared ilock and once again under shared ilock. > > This will race with thing like truncate, hole punching, etc that > serialise IO and invalidate the page cache for data integrity > reasons under the IOLOCK. These rely on there being no IO to the > inode in progress at all to work correctly, which this patch > violates. IOWs, while this is fast, it is not safe and so not a > viable approach to solving the problem. > This statement leaves me wondering, if ext4 does not takes i_rwsem on generic_file_read_iter(), how does ext4 (or any other fs for that matter) guaranty buffered read synchronization with truncate, hole punching etc? The answer in ext4 case is i_mmap_sem, which is read locked in the page fault handler. And xfs does the same type of synchronization with MMAPLOCK, so while my patch may not be safe, I cannot follow why from your explanation, so please explain if I am missing something. One thing that Darrick mentioned earlier was that IOLOCK is also used by xfs to synchronization pNFS leases (probably listed under 'etc' in your explanation). I consent that my patch does not look safe w.r.t pNFS leases, but that can be sorted out with a hammer #ifndef CONFIG_EXPORTFS_BLOCK_OPS or with finer instruments. > FYI, I'm working on a range lock implementation that should both > solve the performance issue and the reader starvation issue at the > same time by allowing concurrent buffered reads and writes to > different file ranges. > > IO range locks will allow proper exclusion for other extent > manipulation operations like fallocate and truncate, and eventually > even allow truncate, hole punch, file extension, etc to run > concurrently with other non-overlapping IO. They solve more than > just the performance issue you are seeing.... > I'm glad to hear that. IO range locks are definitely a more wholesome solution to the problem looking forward. However, I am still interested to continue the discussion on my POC patch. One reason is that I am guessing it would be much easier for distros to backport and pick up to solve performance issues. Even if my patch doesn't get applied upstream nor picked by distros, I would still like to understand its flaws and limitations. I know... if I break it, I get to keep the pieces, but the information that you provide helps me make my risk assessments. Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-05 14:02 ` Amir Goldstein @ 2019-04-07 23:27 ` Dave Chinner 2019-04-08 9:02 ` Amir Goldstein 2019-04-08 11:03 ` Jan Kara 0 siblings, 2 replies; 41+ messages in thread From: Dave Chinner @ 2019-04-07 23:27 UTC (permalink / raw) To: Amir Goldstein Cc: Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > This patch improves performance of mixed random rw workload > > > on xfs without relaxing the atomic buffered read/write guaranty > > > that xfs has always provided. > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > Once with a discard iterator to warm up page cache before taking > > > the shared ilock and once again under shared ilock. > > > > This will race with thing like truncate, hole punching, etc that > > serialise IO and invalidate the page cache for data integrity > > reasons under the IOLOCK. These rely on there being no IO to the > > inode in progress at all to work correctly, which this patch > > violates. IOWs, while this is fast, it is not safe and so not a > > viable approach to solving the problem. > > > > This statement leaves me wondering, if ext4 does not takes > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > fs for that matter) guaranty buffered read synchronization with > truncate, hole punching etc? > The answer in ext4 case is i_mmap_sem, which is read locked > in the page fault handler. Nope, the i_mmap_sem is for serialisation of /page faults/ against truncate, holepunching, etc. Completely irrelevant to the read() path. > And xfs does the same type of synchronization with MMAPLOCK, > so while my patch may not be safe, I cannot follow why from your > explanation, so please explain if I am missing something. mmap_sem inversions require independent locks for IO path and page faults - the MMAPLOCK does not protect anything in the read()/write() IO path. > One thing that Darrick mentioned earlier was that IOLOCK is also > used by xfs to synchronization pNFS leases (probably listed under > 'etc' in your explanation). PNFS leases are separate to the IO locking. All the IO locking does is serialise new IO submission against the process of breaking leases so that extent maps that have been shared under the lease are invalidated correctly. i.e. we can't start IO until the lease has been recalled and the external client has guaranteed it won't read/write data from the stale extent map. If you do IO outside the IOLOCK, then you break those serialisation guarantees and risk data corruption and/or stale data exposure... > I consent that my patch does not look safe > w.r.t pNFS leases, but that can be sorted out with a hammer > #ifndef CONFIG_EXPORTFS_BLOCK_OPS > or with finer instruments. All you see is this: truncate: read() IOLOCK_EXCL flush relevant cached data truncate page cache pre-read page cache between new eof and old eof IOLOCK_SHARED <blocks> start transaction ILOCK_EXCL update isize remove extents .... commit xactn IOLOCK unlock <gets lock> sees beyond EOF, returns 0 So you see the read() doing the right thing (detect EOF, returning short read). Great. But what I see is uptodate pages containing stale data being left in the page cache beyond EOF. That is th eproblem here - truncate must not leave stale pages beyond EOF behind - it's the landmine that causes future things to go wrong. e.g. now the app does post-eof preallocation so the range those pages are cached over are allocated as unwritten - the filesystem will do this without even looking at the page cache because it's beyond EOF. Now we extend the file past those cached pages, and iomap_zero() sees the range as unwritten and so does not write zeros to the blocks between the old EOF and the new EOF. Now the app reads from that range (say it does a sub-page write, triggering a page cache RMW cycle). the read goes to instantiate the page cache page, finds a page already in the cache that is uptodate, and uses it without zeroing or reading from disk. And now we have stale data exposure and/or data corruption. If can come up with quite a few scenarios where this particular "populate cache after invalidation" race can cause similar problems for XFS. Hole punch and most of the other fallocate extent manipulations have the same serialisation requirements - no IO over the range of the operation can be *initiated* between the /start/ of the page cache invalidation and the end of the specific extent manipulation operation. So how does ext4 avoid this problem on truncate? History lesson: truncate in Linux (and hence ext4) has traditionally been serialised by the hacky post-page-lock checks that are strewn all through the page cache and mm/ subsystem. i.e. every time you look up and lock a page cache page, you have to check the page->mapping and page->index to ensure that the lookup-and-lock hasn't raced with truncate. This only works because truncate requires the inode size to be updated before invalidating the page cache - that's the "hacky" part of it. IOWs, the burden of detecting truncate races is strewn throughout the mm/ subsystem, rather than being the responisibility of the filesystem. This is made worse by the fact this mechanism simply doesn't work for hole punching because there is no file size change to indicate that the page lookup is racing with an in-progress invalidation. That means the mm/ and page cache code is unable to detect hole punch races, and so the serialisation of invalidation vs page cache instantiation has to be done in the filesystem. And no Linux native filesystem had the infrastructure for such serialisation because they never had to implement anything to ensure truncate was serialised against new and in-progress IO. The result of this is that, AFAICT, ext4 does not protect against read() vs hole punch races - it's hole punching code it does: Hole Punch: read(): inode_lock() inode_dio_wait(inode); down_write(i_mmap_sem) truncate_pagecache_range() ext4_file_iter_read() ext4_map_blocks() down_read(i_data_sem) <gets mapping> <populates page cache over hole> <reads stale data into cache> ..... down_write(i_data_sem) remove extents IOWs, ext4 is safe against truncate because of the change-inode-size-before-invalidation hacks, but the lack of serialise buffered reads means that hole punch and other similar fallocate based extent manipulations can race against reads.... > However, I am still interested to continue the discussion on my POC > patch. One reason is that I am guessing it would be much easier for > distros to backport and pick up to solve performance issues. Upstream first, please. If it's not fit for upstream, then it most definitely is not fit for backporting to distro kernels. Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-07 23:27 ` Dave Chinner @ 2019-04-08 9:02 ` Amir Goldstein 2019-04-08 14:11 ` Jan Kara 2019-04-08 11:03 ` Jan Kara 1 sibling, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2019-04-08 9:02 UTC (permalink / raw) To: Dave Chinner Cc: Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso, Jan Kara On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > This patch improves performance of mixed random rw workload > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > that xfs has always provided. > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > Once with a discard iterator to warm up page cache before taking > > > > the shared ilock and once again under shared ilock. > > > > > > This will race with thing like truncate, hole punching, etc that > > > serialise IO and invalidate the page cache for data integrity > > > reasons under the IOLOCK. These rely on there being no IO to the > > > inode in progress at all to work correctly, which this patch > > > violates. IOWs, while this is fast, it is not safe and so not a > > > viable approach to solving the problem. > > > > > > > This statement leaves me wondering, if ext4 does not takes > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > fs for that matter) guaranty buffered read synchronization with > > truncate, hole punching etc? > > The answer in ext4 case is i_mmap_sem, which is read locked > > in the page fault handler. > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > truncate, holepunching, etc. Completely irrelevant to the read() > path. > I'm at lost here. Why are page faults completely irrelevant to read() path? Aren't full pages supposed to be faulted in on read() after truncate_pagecache_range()? And aren't partial pages supposed to be partially zeroed and uptodate after truncate_pagecache_range()? > > And xfs does the same type of synchronization with MMAPLOCK, > > so while my patch may not be safe, I cannot follow why from your > > explanation, so please explain if I am missing something. > > mmap_sem inversions require independent locks for IO path and page > faults - the MMAPLOCK does not protect anything in the > read()/write() IO path. > [...] > > All you see is this: > > truncate: read() > > IOLOCK_EXCL > flush relevant cached data > truncate page cache > pre-read page cache between > new eof and old eof > IOLOCK_SHARED > <blocks> > start transaction > ILOCK_EXCL > update isize > remove extents > .... > commit xactn > IOLOCK unlock > <gets lock> > sees beyond EOF, returns 0 > > > So you see the read() doing the right thing (detect EOF, returning > short read). Great. > > But what I see is uptodate pages containing stale data being left in > the page cache beyond EOF. That is th eproblem here - truncate must > not leave stale pages beyond EOF behind - it's the landmine that > causes future things to go wrong. > > e.g. now the app does post-eof preallocation so the range those > pages are cached over are allocated as unwritten - the filesystem > will do this without even looking at the page cache because it's > beyond EOF. Now we extend the file past those cached pages, and > iomap_zero() sees the range as unwritten and so does not write zeros > to the blocks between the old EOF and the new EOF. Now the app reads > from that range (say it does a sub-page write, triggering a page > cache RMW cycle). the read goes to instantiate the page cache page, > finds a page already in the cache that is uptodate, and uses it > without zeroing or reading from disk. > > And now we have stale data exposure and/or data corruption. > > If can come up with quite a few scenarios where this particular > "populate cache after invalidation" race can cause similar problems > for XFS. Hole punch and most of the other fallocate extent > manipulations have the same serialisation requirements - no IO over > the range of the operation can be *initiated* between the /start/ of > the page cache invalidation and the end of the specific extent > manipulation operation. > > So how does ext4 avoid this problem on truncate? > > History lesson: truncate in Linux (and hence ext4) has traditionally > been serialised by the hacky post-page-lock checks that are strewn > all through the page cache and mm/ subsystem. i.e. every time you > look up and lock a page cache page, you have to check the > page->mapping and page->index to ensure that the lookup-and-lock > hasn't raced with truncate. This only works because truncate > requires the inode size to be updated before invalidating the page > cache - that's the "hacky" part of it. > > IOWs, the burden of detecting truncate races is strewn throughout > the mm/ subsystem, rather than being the responisibility of the > filesystem. This is made worse by the fact this mechanism simply > doesn't work for hole punching because there is no file size change > to indicate that the page lookup is racing with an in-progress > invalidation. > > That means the mm/ and page cache code is unable to detect hole > punch races, and so the serialisation of invalidation vs page cache > instantiation has to be done in the filesystem. And no Linux native > filesystem had the infrastructure for such serialisation because > they never had to implement anything to ensure truncate was > serialised against new and in-progress IO. > > The result of this is that, AFAICT, ext4 does not protect against > read() vs hole punch races - it's hole punching code it does: > > Hole Punch: read(): > > inode_lock() > inode_dio_wait(inode); > down_write(i_mmap_sem) > truncate_pagecache_range() > ext4_file_iter_read() > ext4_map_blocks() > down_read(i_data_sem) > <gets mapping> > <populates page cache over hole> > <reads stale data into cache> > ..... > down_write(i_data_sem) > remove extents > > IOWs, ext4 is safe against truncate because of the > change-inode-size-before-invalidation hacks, but the lack of > serialise buffered reads means that hole punch and other similar > fallocate based extent manipulations can race against reads.... > Adding some ext4 folks to comment on the above. Could it be that those races were already addressed by Lukas' work: https://lore.kernel.org/patchwork/cover/371861/ Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 9:02 ` Amir Goldstein @ 2019-04-08 14:11 ` Jan Kara 2019-04-08 17:41 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2019-04-08 14:11 UTC (permalink / raw) To: Amir Goldstein Cc: Dave Chinner, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso, Jan Kara On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > This patch improves performance of mixed random rw workload > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > that xfs has always provided. > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > Once with a discard iterator to warm up page cache before taking > > > > > the shared ilock and once again under shared ilock. > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > serialise IO and invalidate the page cache for data integrity > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > inode in progress at all to work correctly, which this patch > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > viable approach to solving the problem. > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > fs for that matter) guaranty buffered read synchronization with > > > truncate, hole punching etc? > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > in the page fault handler. > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > truncate, holepunching, etc. Completely irrelevant to the read() > > path. > > > > I'm at lost here. Why are page faults completely irrelevant to read() > path? Aren't full pages supposed to be faulted in on read() after > truncate_pagecache_range()? During read(2), pages are not "faulted in". Just look at what generic_file_buffered_read() does. It uses completely separate code to add page to page cache, trigger readahead, and possibly call ->readpage() to fill the page with data. "fault" path (handled by filemap_fault()) applies only to accesses from userspace to mmaps. > And aren't partial pages supposed to be partially zeroed and uptodate > after truncate_pagecache_range()? truncate_pagecache_range() does take care of page zeroing, that is correct (if those pages are in page cache in the first place). I'm not sure how this relates to the above discussion though. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 14:11 ` Jan Kara @ 2019-04-08 17:41 ` Amir Goldstein 2019-04-09 8:26 ` Jan Kara 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2019-04-08 17:41 UTC (permalink / raw) To: Jan Kara Cc: Dave Chinner, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > This patch improves performance of mixed random rw workload > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > that xfs has always provided. > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > serialise IO and invalidate the page cache for data integrity > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > inode in progress at all to work correctly, which this patch > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > viable approach to solving the problem. > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > fs for that matter) guaranty buffered read synchronization with > > > > truncate, hole punching etc? > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > in the page fault handler. > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > path. > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > path? Aren't full pages supposed to be faulted in on read() after > > truncate_pagecache_range()? > > During read(2), pages are not "faulted in". Just look at > what generic_file_buffered_read() does. It uses completely separate code to > add page to page cache, trigger readahead, and possibly call ->readpage() to > fill the page with data. "fault" path (handled by filemap_fault()) applies > only to accesses from userspace to mmaps. > Oh! thanks for fixing my blind spot. So if you agree with Dave that ext4, and who knows what other fs, are vulnerable to populating page cache with stale "uptodate" data, then it seems to me that also xfs is vulnerable via readahead(2) and posix_fadvise(). Mind you, I recently added an fadvise f_op, so it could be used by xfs to synchronize with IOLOCK. Perhaps a better solution would be for truncate_pagecache_range() to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page cache. When we have shared pages for files, these pages could be deduped. Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 17:41 ` Amir Goldstein @ 2019-04-09 8:26 ` Jan Kara 2022-06-17 14:48 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2019-04-09 8:26 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Dave Chinner, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso, Al Viro On Mon 08-04-19 20:41:09, Amir Goldstein wrote: > On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > > This patch improves performance of mixed random rw workload > > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > > that xfs has always provided. > > > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > > serialise IO and invalidate the page cache for data integrity > > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > > inode in progress at all to work correctly, which this patch > > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > > viable approach to solving the problem. > > > > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > > fs for that matter) guaranty buffered read synchronization with > > > > > truncate, hole punching etc? > > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > > in the page fault handler. > > > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > > path. > > > > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > > path? Aren't full pages supposed to be faulted in on read() after > > > truncate_pagecache_range()? > > > > During read(2), pages are not "faulted in". Just look at > > what generic_file_buffered_read() does. It uses completely separate code to > > add page to page cache, trigger readahead, and possibly call ->readpage() to > > fill the page with data. "fault" path (handled by filemap_fault()) applies > > only to accesses from userspace to mmaps. > > > > Oh! thanks for fixing my blind spot. > So if you agree with Dave that ext4, and who knows what other fs, > are vulnerable to populating page cache with stale "uptodate" data, Not that many filesystems support punching holes but you're right. > then it seems to me that also xfs is vulnerable via readahead(2) and > posix_fadvise(). Yes, this is correct AFAICT. > Mind you, I recently added an fadvise f_op, so it could be used by > xfs to synchronize with IOLOCK. And yes, this should work. > Perhaps a better solution would be for truncate_pagecache_range() > to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page > cache. When we have shared pages for files, these pages could be > deduped. No, I wouldn't really mess with sharing pages due to this. It would be hard to make that scale resonably and would be rather complex. We really need a proper and reasonably simple synchronization mechanism between operations removing blocks from inode and operations filling in page cache of the inode. Page lock was supposed to provide this but doesn't quite work because hole punching first remove pagecache pages and then go removing all blocks. So I agree with Dave that going for range lock is really the cleanest way forward here without causing big regressions for mixed rw workloads. I'm just thinking how to best do that without introducing lot of boilerplate code into each filesystem. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-09 8:26 ` Jan Kara @ 2022-06-17 14:48 ` Amir Goldstein 2022-06-17 15:11 ` Jan Kara 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-06-17 14:48 UTC (permalink / raw) To: Jan Kara Cc: Dave Chinner, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso, Al Viro On Tue, Apr 9, 2019 at 11:26 AM Jan Kara <jack@suse.cz> wrote: > > On Mon 08-04-19 20:41:09, Amir Goldstein wrote: > > On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > > > > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > > > This patch improves performance of mixed random rw workload > > > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > > > that xfs has always provided. > > > > > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > > > serialise IO and invalidate the page cache for data integrity > > > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > > > inode in progress at all to work correctly, which this patch > > > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > > > viable approach to solving the problem. > > > > > > > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > > > fs for that matter) guaranty buffered read synchronization with > > > > > > truncate, hole punching etc? > > > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > > > in the page fault handler. > > > > > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > > > path. > > > > > > > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > > > path? Aren't full pages supposed to be faulted in on read() after > > > > truncate_pagecache_range()? > > > > > > During read(2), pages are not "faulted in". Just look at > > > what generic_file_buffered_read() does. It uses completely separate code to > > > add page to page cache, trigger readahead, and possibly call ->readpage() to > > > fill the page with data. "fault" path (handled by filemap_fault()) applies > > > only to accesses from userspace to mmaps. > > > > > > > Oh! thanks for fixing my blind spot. > > So if you agree with Dave that ext4, and who knows what other fs, > > are vulnerable to populating page cache with stale "uptodate" data, > > Not that many filesystems support punching holes but you're right. > > > then it seems to me that also xfs is vulnerable via readahead(2) and > > posix_fadvise(). > > Yes, this is correct AFAICT. > > > Mind you, I recently added an fadvise f_op, so it could be used by > > xfs to synchronize with IOLOCK. > > And yes, this should work. > > > Perhaps a better solution would be for truncate_pagecache_range() > > to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page > > cache. When we have shared pages for files, these pages could be > > deduped. > > No, I wouldn't really mess with sharing pages due to this. It would be hard > to make that scale resonably and would be rather complex. We really need a > proper and reasonably simple synchronization mechanism between operations > removing blocks from inode and operations filling in page cache of the > inode. Page lock was supposed to provide this but doesn't quite work > because hole punching first remove pagecache pages and then go removing all > blocks. > > So I agree with Dave that going for range lock is really the cleanest way > forward here without causing big regressions for mixed rw workloads. I'm > just thinking how to best do that without introducing lot of boilerplate > code into each filesystem. Hi Jan, Dave, Trying to circle back to this after 3 years! Seeing that there is no progress with range locks and that the mixed rw workloads performance issue still very much exists. Is the situation now different than 3 years ago with invalidate_lock? Would my approach of pre-warm page cache before taking IOLOCK be safe if page cache is pre-warmed with invalidate_lock held? For the pNFS leases issue, as I wrote back in pre-COVID era, I intend to opt-out of this optimization with #ifndef CONFIG_EXPORTFS_BLOCK_OPS Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-17 14:48 ` Amir Goldstein @ 2022-06-17 15:11 ` Jan Kara 2022-06-18 8:38 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2022-06-17 15:11 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Dave Chinner, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Ext4, Lukas Czerner, Theodore Tso, Al Viro On Fri 17-06-22 17:48:08, Amir Goldstein wrote: > On Tue, Apr 9, 2019 at 11:26 AM Jan Kara <jack@suse.cz> wrote: > > > > On Mon 08-04-19 20:41:09, Amir Goldstein wrote: > > > On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > > > > > > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > > > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > > > > This patch improves performance of mixed random rw workload > > > > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > > > > that xfs has always provided. > > > > > > > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > > > > serialise IO and invalidate the page cache for data integrity > > > > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > > > > inode in progress at all to work correctly, which this patch > > > > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > > > > viable approach to solving the problem. > > > > > > > > > > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > > > > fs for that matter) guaranty buffered read synchronization with > > > > > > > truncate, hole punching etc? > > > > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > > > > in the page fault handler. > > > > > > > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > > > > path. > > > > > > > > > > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > > > > path? Aren't full pages supposed to be faulted in on read() after > > > > > truncate_pagecache_range()? > > > > > > > > During read(2), pages are not "faulted in". Just look at > > > > what generic_file_buffered_read() does. It uses completely separate code to > > > > add page to page cache, trigger readahead, and possibly call ->readpage() to > > > > fill the page with data. "fault" path (handled by filemap_fault()) applies > > > > only to accesses from userspace to mmaps. > > > > > > > > > > Oh! thanks for fixing my blind spot. > > > So if you agree with Dave that ext4, and who knows what other fs, > > > are vulnerable to populating page cache with stale "uptodate" data, > > > > Not that many filesystems support punching holes but you're right. > > > > > then it seems to me that also xfs is vulnerable via readahead(2) and > > > posix_fadvise(). > > > > Yes, this is correct AFAICT. > > > > > Mind you, I recently added an fadvise f_op, so it could be used by > > > xfs to synchronize with IOLOCK. > > > > And yes, this should work. > > > > > Perhaps a better solution would be for truncate_pagecache_range() > > > to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page > > > cache. When we have shared pages for files, these pages could be > > > deduped. > > > > No, I wouldn't really mess with sharing pages due to this. It would be hard > > to make that scale resonably and would be rather complex. We really need a > > proper and reasonably simple synchronization mechanism between operations > > removing blocks from inode and operations filling in page cache of the > > inode. Page lock was supposed to provide this but doesn't quite work > > because hole punching first remove pagecache pages and then go removing all > > blocks. > > > > So I agree with Dave that going for range lock is really the cleanest way > > forward here without causing big regressions for mixed rw workloads. I'm > > just thinking how to best do that without introducing lot of boilerplate > > code into each filesystem. > > Hi Jan, Dave, > > Trying to circle back to this after 3 years! > Seeing that there is no progress with range locks and > that the mixed rw workloads performance issue still very much exists. > > Is the situation now different than 3 years ago with invalidate_lock? Yes, I've implemented invalidate_lock exactly to fix the issues you've pointed out without regressing the mixed rw workloads (because invalidate_lock is taken in shared mode only for reads and usually not at all for writes). > Would my approach of pre-warm page cache before taking IOLOCK > be safe if page cache is pre-warmed with invalidate_lock held? Why would it be needed? But yes, with invalidate_lock you could presumably make that idea safe... Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-17 15:11 ` Jan Kara @ 2022-06-18 8:38 ` Amir Goldstein 2022-06-20 9:11 ` Jan Kara 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-06-18 8:38 UTC (permalink / raw) To: Jan Kara, Darrick J . Wong Cc: Dave Chinner, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Fri, Jun 17, 2022 at 6:11 PM Jan Kara <jack@suse.cz> wrote: > > On Fri 17-06-22 17:48:08, Amir Goldstein wrote: > > On Tue, Apr 9, 2019 at 11:26 AM Jan Kara <jack@suse.cz> wrote: > > > > > > On Mon 08-04-19 20:41:09, Amir Goldstein wrote: > > > > On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > > > > > > > > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > > > > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > > > > > This patch improves performance of mixed random rw workload > > > > > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > > > > > that xfs has always provided. > > > > > > > > > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > > > > > serialise IO and invalidate the page cache for data integrity > > > > > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > > > > > inode in progress at all to work correctly, which this patch > > > > > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > > > > > viable approach to solving the problem. > > > > > > > > > > > > > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > > > > > fs for that matter) guaranty buffered read synchronization with > > > > > > > > truncate, hole punching etc? > > > > > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > > > > > in the page fault handler. > > > > > > > > > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > > > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > > > > > path. > > > > > > > > > > > > > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > > > > > path? Aren't full pages supposed to be faulted in on read() after > > > > > > truncate_pagecache_range()? > > > > > > > > > > During read(2), pages are not "faulted in". Just look at > > > > > what generic_file_buffered_read() does. It uses completely separate code to > > > > > add page to page cache, trigger readahead, and possibly call ->readpage() to > > > > > fill the page with data. "fault" path (handled by filemap_fault()) applies > > > > > only to accesses from userspace to mmaps. > > > > > > > > > > > > > Oh! thanks for fixing my blind spot. > > > > So if you agree with Dave that ext4, and who knows what other fs, > > > > are vulnerable to populating page cache with stale "uptodate" data, > > > > > > Not that many filesystems support punching holes but you're right. > > > > > > > then it seems to me that also xfs is vulnerable via readahead(2) and > > > > posix_fadvise(). > > > > > > Yes, this is correct AFAICT. > > > > > > > Mind you, I recently added an fadvise f_op, so it could be used by > > > > xfs to synchronize with IOLOCK. > > > > > > And yes, this should work. > > > > > > > Perhaps a better solution would be for truncate_pagecache_range() > > > > to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page > > > > cache. When we have shared pages for files, these pages could be > > > > deduped. > > > > > > No, I wouldn't really mess with sharing pages due to this. It would be hard > > > to make that scale resonably and would be rather complex. We really need a > > > proper and reasonably simple synchronization mechanism between operations > > > removing blocks from inode and operations filling in page cache of the > > > inode. Page lock was supposed to provide this but doesn't quite work > > > because hole punching first remove pagecache pages and then go removing all > > > blocks. > > > > > > So I agree with Dave that going for range lock is really the cleanest way > > > forward here without causing big regressions for mixed rw workloads. I'm > > > just thinking how to best do that without introducing lot of boilerplate > > > code into each filesystem. > > > > Hi Jan, Dave, > > > > Trying to circle back to this after 3 years! > > Seeing that there is no progress with range locks and > > that the mixed rw workloads performance issue still very much exists. > > > > Is the situation now different than 3 years ago with invalidate_lock? > > Yes, I've implemented invalidate_lock exactly to fix the issues you've > pointed out without regressing the mixed rw workloads (because > invalidate_lock is taken in shared mode only for reads and usually not at > all for writes). > > > Would my approach of pre-warm page cache before taking IOLOCK > > be safe if page cache is pre-warmed with invalidate_lock held? > > Why would it be needed? But yes, with invalidate_lock you could presumably > make that idea safe... To remind you, the context in which I pointed you to the punch hole race issue in "other file systems" was a discussion about trying to relax the "atomic write" POSIX semantics [1] of xfs. There was a lot of discussions around range locks and changing the fairness of rwsem readers and writer, but none of this changes the fact that as long as the lock is file wide (and it does not look like that is going to change in the near future), it is better for lock contention to perform the serialization on page cache read/write and not on disk read/write. Therefore, *if* it is acceptable to pre-warn page cache for buffered read under invalidate_lock, that is a simple way to bring the xfs performance with random rw mix workload on par with ext4 performance without losing the atomic write POSIX semantics. So everyone can be happy? In addition to Dave's concerns about stale page cache races with hole punch, I found in the original discussion these concern from Darrick: > Reads and writes are not the only thing xfs uses i_rwsem to synchronise. > Reflink remap uses it to make sure everything's flushed to disk and that > page cache contents remain clean while the remap is ongoing. I'm pretty > sure pnfs uses it for similar reasons when granting and committing write > leases. To reiterate, pNFS leases are not the common case. To address this issue, I intend to opt-out of pre-warm optimization when pNFS leases are present, either globally, or per file, whatever xfs developers tell me to do. From my understanding of the code, xfs_reflink_remap_prep() takes care of taking invalidate_lock(s), so populating page cache under invalidate_lock should be safe also w.r.t reflink/dedupe. Darrick, am I missing anything? Thanks, Amir. [1] https://lore.kernel.org/all/CAOQ4uxgSc7hK1=GuUajzG1Z+ks6gzFFX+EtuBMULOk0s85zi3A@mail.gmail.com/ [2] https://lore.kernel.org/linux-xfs/20190325154731.GT1183@magnolia/ ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-18 8:38 ` Amir Goldstein @ 2022-06-20 9:11 ` Jan Kara 2022-06-21 7:49 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2022-06-20 9:11 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Darrick J . Wong, Dave Chinner, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Sat 18-06-22 11:38:30, Amir Goldstein wrote: > On Fri, Jun 17, 2022 at 6:11 PM Jan Kara <jack@suse.cz> wrote: > > > > On Fri 17-06-22 17:48:08, Amir Goldstein wrote: > > > On Tue, Apr 9, 2019 at 11:26 AM Jan Kara <jack@suse.cz> wrote: > > > > > > > > On Mon 08-04-19 20:41:09, Amir Goldstein wrote: > > > > > On Mon, Apr 8, 2019 at 5:11 PM Jan Kara <jack@suse.cz> wrote: > > > > > > > > > > > > On Mon 08-04-19 12:02:34, Amir Goldstein wrote: > > > > > > > On Mon, Apr 8, 2019 at 2:27 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > > > On Fri, Apr 05, 2019 at 05:02:33PM +0300, Amir Goldstein wrote: > > > > > > > > > On Fri, Apr 5, 2019 at 12:17 AM Dave Chinner <david@fromorbit.com> wrote: > > > > > > > > > > > > > > > > > > > > On Thu, Apr 04, 2019 at 07:57:37PM +0300, Amir Goldstein wrote: > > > > > > > > > > > This patch improves performance of mixed random rw workload > > > > > > > > > > > on xfs without relaxing the atomic buffered read/write guaranty > > > > > > > > > > > that xfs has always provided. > > > > > > > > > > > > > > > > > > > > > > We achieve that by calling generic_file_read_iter() twice. > > > > > > > > > > > Once with a discard iterator to warm up page cache before taking > > > > > > > > > > > the shared ilock and once again under shared ilock. > > > > > > > > > > > > > > > > > > > > This will race with thing like truncate, hole punching, etc that > > > > > > > > > > serialise IO and invalidate the page cache for data integrity > > > > > > > > > > reasons under the IOLOCK. These rely on there being no IO to the > > > > > > > > > > inode in progress at all to work correctly, which this patch > > > > > > > > > > violates. IOWs, while this is fast, it is not safe and so not a > > > > > > > > > > viable approach to solving the problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > This statement leaves me wondering, if ext4 does not takes > > > > > > > > > i_rwsem on generic_file_read_iter(), how does ext4 (or any other > > > > > > > > > fs for that matter) guaranty buffered read synchronization with > > > > > > > > > truncate, hole punching etc? > > > > > > > > > The answer in ext4 case is i_mmap_sem, which is read locked > > > > > > > > > in the page fault handler. > > > > > > > > > > > > > > > > Nope, the i_mmap_sem is for serialisation of /page faults/ against > > > > > > > > truncate, holepunching, etc. Completely irrelevant to the read() > > > > > > > > path. > > > > > > > > > > > > > > > > > > > > > > I'm at lost here. Why are page faults completely irrelevant to read() > > > > > > > path? Aren't full pages supposed to be faulted in on read() after > > > > > > > truncate_pagecache_range()? > > > > > > > > > > > > During read(2), pages are not "faulted in". Just look at > > > > > > what generic_file_buffered_read() does. It uses completely separate code to > > > > > > add page to page cache, trigger readahead, and possibly call ->readpage() to > > > > > > fill the page with data. "fault" path (handled by filemap_fault()) applies > > > > > > only to accesses from userspace to mmaps. > > > > > > > > > > > > > > > > Oh! thanks for fixing my blind spot. > > > > > So if you agree with Dave that ext4, and who knows what other fs, > > > > > are vulnerable to populating page cache with stale "uptodate" data, > > > > > > > > Not that many filesystems support punching holes but you're right. > > > > > > > > > then it seems to me that also xfs is vulnerable via readahead(2) and > > > > > posix_fadvise(). > > > > > > > > Yes, this is correct AFAICT. > > > > > > > > > Mind you, I recently added an fadvise f_op, so it could be used by > > > > > xfs to synchronize with IOLOCK. > > > > > > > > And yes, this should work. > > > > > > > > > Perhaps a better solution would be for truncate_pagecache_range() > > > > > to leave zeroed or Unwritten (i.e. lazy zeroed by read) pages in page > > > > > cache. When we have shared pages for files, these pages could be > > > > > deduped. > > > > > > > > No, I wouldn't really mess with sharing pages due to this. It would be hard > > > > to make that scale resonably and would be rather complex. We really need a > > > > proper and reasonably simple synchronization mechanism between operations > > > > removing blocks from inode and operations filling in page cache of the > > > > inode. Page lock was supposed to provide this but doesn't quite work > > > > because hole punching first remove pagecache pages and then go removing all > > > > blocks. > > > > > > > > So I agree with Dave that going for range lock is really the cleanest way > > > > forward here without causing big regressions for mixed rw workloads. I'm > > > > just thinking how to best do that without introducing lot of boilerplate > > > > code into each filesystem. > > > > > > Hi Jan, Dave, > > > > > > Trying to circle back to this after 3 years! > > > Seeing that there is no progress with range locks and > > > that the mixed rw workloads performance issue still very much exists. > > > > > > Is the situation now different than 3 years ago with invalidate_lock? > > > > Yes, I've implemented invalidate_lock exactly to fix the issues you've > > pointed out without regressing the mixed rw workloads (because > > invalidate_lock is taken in shared mode only for reads and usually not at > > all for writes). > > > > > Would my approach of pre-warm page cache before taking IOLOCK > > > be safe if page cache is pre-warmed with invalidate_lock held? > > > > Why would it be needed? But yes, with invalidate_lock you could presumably > > make that idea safe... > > To remind you, the context in which I pointed you to the punch hole race > issue in "other file systems" was a discussion about trying to relax the > "atomic write" POSIX semantics [1] of xfs. Ah, I see. Sorry, I already forgot :-| > There was a lot of discussions around range locks and changing the > fairness of rwsem readers and writer, but none of this changes the fact > that as long as the lock is file wide (and it does not look like that is > going to change in the near future), it is better for lock contention to > perform the serialization on page cache read/write and not on disk > read/write. > > Therefore, *if* it is acceptable to pre-warn page cache for buffered read > under invalidate_lock, that is a simple way to bring the xfs performance with > random rw mix workload on par with ext4 performance without losing the > atomic write POSIX semantics. So everyone can be happy? So to spell out your proposal so that we are on the same page: you want to use invalidate_lock + page locks to achieve "writes are atomic wrt reads" property XFS currently has without holding i_rwsem in shared mode during reads. Am I getting it correct? How exactly do you imagine the synchronization of buffered read against buffered write would work? Lock all pages for the read range in the page cache? You'd need to be careful to not bring the machine OOM when someone asks to read a huge range... Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-20 9:11 ` Jan Kara @ 2022-06-21 7:49 ` Amir Goldstein 2022-06-21 8:59 ` Jan Kara 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-06-21 7:49 UTC (permalink / raw) To: Jan Kara Cc: Darrick J . Wong, Dave Chinner, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel > > > > Hi Jan, Dave, > > > > > > > > Trying to circle back to this after 3 years! > > > > Seeing that there is no progress with range locks and > > > > that the mixed rw workloads performance issue still very much exists. > > > > > > > > Is the situation now different than 3 years ago with invalidate_lock? > > > > > > Yes, I've implemented invalidate_lock exactly to fix the issues you've > > > pointed out without regressing the mixed rw workloads (because > > > invalidate_lock is taken in shared mode only for reads and usually not at > > > all for writes). > > > > > > > Would my approach of pre-warm page cache before taking IOLOCK > > > > be safe if page cache is pre-warmed with invalidate_lock held? > > > > > > Why would it be needed? But yes, with invalidate_lock you could presumably > > > make that idea safe... > > > > To remind you, the context in which I pointed you to the punch hole race > > issue in "other file systems" was a discussion about trying to relax the > > "atomic write" POSIX semantics [1] of xfs. > > Ah, I see. Sorry, I already forgot :-| Understandable. It has been 3 years ;-) > > > There was a lot of discussions around range locks and changing the > > fairness of rwsem readers and writer, but none of this changes the fact > > that as long as the lock is file wide (and it does not look like that is > > going to change in the near future), it is better for lock contention to > > perform the serialization on page cache read/write and not on disk > > read/write. > > > > Therefore, *if* it is acceptable to pre-warn page cache for buffered read > > under invalidate_lock, that is a simple way to bring the xfs performance with > > random rw mix workload on par with ext4 performance without losing the > > atomic write POSIX semantics. So everyone can be happy? > > So to spell out your proposal so that we are on the same page: you want to > use invalidate_lock + page locks to achieve "writes are atomic wrt reads" > property XFS currently has without holding i_rwsem in shared mode during > reads. Am I getting it correct? Not exactly. > > How exactly do you imagine the synchronization of buffered read against > buffered write would work? Lock all pages for the read range in the page > cache? You'd need to be careful to not bring the machine OOM when someone > asks to read a huge range... I imagine that the atomic r/w synchronisation will remain *exactly* as it is today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), when reading data into user buffer, but before that, I would like to issue and wait for read of the pages in the range to reduce the probability of doing the read I/O under XFS_IOLOCK_SHARED. The pre-warm of page cache does not need to abide to the atomic read semantics and it is also tolerable if some pages are evicted in between pre-warn and read to user buffer - in the worst case this will result in I/O amplification, but for the common case, it will be a big win for the mixed random r/w performance on xfs. To reduce risk of page cache thrashing we can limit this optimization to a maximum number of page cache pre-warm. The questions are: 1. Does this plan sound reasonable? 2. Is there a ready helper (force_page_cache_readahead?) that I can use which takes the required page/invalidate locks? Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-21 7:49 ` Amir Goldstein @ 2022-06-21 8:59 ` Jan Kara 2022-06-21 12:53 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2022-06-21 8:59 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Darrick J . Wong, Dave Chinner, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > How exactly do you imagine the synchronization of buffered read against > > buffered write would work? Lock all pages for the read range in the page > > cache? You'd need to be careful to not bring the machine OOM when someone > > asks to read a huge range... > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > when reading data into user buffer, but before that, I would like to issue > and wait for read of the pages in the range to reduce the probability > of doing the read I/O under XFS_IOLOCK_SHARED. > > The pre-warm of page cache does not need to abide to the atomic read > semantics and it is also tolerable if some pages are evicted in between > pre-warn and read to user buffer - in the worst case this will result in > I/O amplification, but for the common case, it will be a big win for the > mixed random r/w performance on xfs. > > To reduce risk of page cache thrashing we can limit this optimization > to a maximum number of page cache pre-warm. > > The questions are: > 1. Does this plan sound reasonable? Ah, I see now. So essentially the idea is to pull the readahead (which is currently happening from filemap_read() -> filemap_get_pages()) out from under the i_rwsem. It looks like a fine idea to me. > 2. Is there a ready helper (force_page_cache_readahead?) that > I can use which takes the required page/invalidate locks? page_cache_sync_readahead() should be the function you need. It does take care to lock invalidate_lock internally when creating & reading pages. I just cannot comment on whether calling this without i_rwsem does not break some internal XFS expectations for stuff like reflink etc. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-21 8:59 ` Jan Kara @ 2022-06-21 12:53 ` Amir Goldstein 2022-06-22 3:23 ` Matthew Wilcox 2022-09-13 14:40 ` Amir Goldstein 0 siblings, 2 replies; 41+ messages in thread From: Amir Goldstein @ 2022-06-21 12:53 UTC (permalink / raw) To: Jan Kara Cc: Darrick J . Wong, Dave Chinner, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > How exactly do you imagine the synchronization of buffered read against > > > buffered write would work? Lock all pages for the read range in the page > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > asks to read a huge range... > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > when reading data into user buffer, but before that, I would like to issue > > and wait for read of the pages in the range to reduce the probability > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > The pre-warm of page cache does not need to abide to the atomic read > > semantics and it is also tolerable if some pages are evicted in between > > pre-warn and read to user buffer - in the worst case this will result in > > I/O amplification, but for the common case, it will be a big win for the > > mixed random r/w performance on xfs. > > > > To reduce risk of page cache thrashing we can limit this optimization > > to a maximum number of page cache pre-warm. > > > > The questions are: > > 1. Does this plan sound reasonable? > > Ah, I see now. So essentially the idea is to pull the readahead (which is > currently happening from filemap_read() -> filemap_get_pages()) out from under > the i_rwsem. It looks like a fine idea to me. Great! Anyone doesn't like the idea or has another suggestion? > > > 2. Is there a ready helper (force_page_cache_readahead?) that > > I can use which takes the required page/invalidate locks? > > page_cache_sync_readahead() should be the function you need. It does take > care to lock invalidate_lock internally when creating & reading pages. I Thanks, I'll try that. > just cannot comment on whether calling this without i_rwsem does not break > some internal XFS expectations for stuff like reflink etc. relink is done under xfs_ilock2_io_mmap => filemap_invalidate_lock_two so it should not be a problem. pNFS leases I need to look into. Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-21 12:53 ` Amir Goldstein @ 2022-06-22 3:23 ` Matthew Wilcox 2022-06-22 9:00 ` Amir Goldstein 2022-09-13 14:40 ` Amir Goldstein 1 sibling, 1 reply; 41+ messages in thread From: Matthew Wilcox @ 2022-06-22 3:23 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Darrick J . Wong, Dave Chinner, Christoph Hellwig, linux-xfs, linux-fsdevel On Tue, Jun 21, 2022 at 03:53:33PM +0300, Amir Goldstein wrote: > On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > > How exactly do you imagine the synchronization of buffered read against > > > > buffered write would work? Lock all pages for the read range in the page > > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > > asks to read a huge range... > > > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > > when reading data into user buffer, but before that, I would like to issue > > > and wait for read of the pages in the range to reduce the probability > > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > > > The pre-warm of page cache does not need to abide to the atomic read > > > semantics and it is also tolerable if some pages are evicted in between > > > pre-warn and read to user buffer - in the worst case this will result in > > > I/O amplification, but for the common case, it will be a big win for the > > > mixed random r/w performance on xfs. > > > > > > To reduce risk of page cache thrashing we can limit this optimization > > > to a maximum number of page cache pre-warm. > > > > > > The questions are: > > > 1. Does this plan sound reasonable? > > > > Ah, I see now. So essentially the idea is to pull the readahead (which is > > currently happening from filemap_read() -> filemap_get_pages()) out from under > > the i_rwsem. It looks like a fine idea to me. > > Great! > Anyone doesn't like the idea or has another suggestion? I guess I'm still confused. The problem was the the XFS IOLOCK was being held while we waited for readahead to complete. To fix this, you're planning on waiting for readahead to complete with the invalidate lock held? I don't see the benefit. I see the invalidate_lock as being roughly equivalent to the IOLOCK, just pulled up to the VFS. Is that incorrect? ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-22 3:23 ` Matthew Wilcox @ 2022-06-22 9:00 ` Amir Goldstein 2022-06-22 9:34 ` Jan Kara 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-06-22 9:00 UTC (permalink / raw) To: Matthew Wilcox Cc: Jan Kara, Darrick J . Wong, Dave Chinner, Christoph Hellwig, linux-xfs, linux-fsdevel On Wed, Jun 22, 2022 at 6:23 AM Matthew Wilcox <willy@infradead.org> wrote: > > On Tue, Jun 21, 2022 at 03:53:33PM +0300, Amir Goldstein wrote: > > On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > > > > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > > > How exactly do you imagine the synchronization of buffered read against > > > > > buffered write would work? Lock all pages for the read range in the page > > > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > > > asks to read a huge range... > > > > > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > > > when reading data into user buffer, but before that, I would like to issue > > > > and wait for read of the pages in the range to reduce the probability > > > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > > > > > The pre-warm of page cache does not need to abide to the atomic read > > > > semantics and it is also tolerable if some pages are evicted in between > > > > pre-warn and read to user buffer - in the worst case this will result in > > > > I/O amplification, but for the common case, it will be a big win for the > > > > mixed random r/w performance on xfs. > > > > > > > > To reduce risk of page cache thrashing we can limit this optimization > > > > to a maximum number of page cache pre-warm. > > > > > > > > The questions are: > > > > 1. Does this plan sound reasonable? > > > > > > Ah, I see now. So essentially the idea is to pull the readahead (which is > > > currently happening from filemap_read() -> filemap_get_pages()) out from under > > > the i_rwsem. It looks like a fine idea to me. > > > > Great! > > Anyone doesn't like the idea or has another suggestion? > > I guess I'm still confused. > > The problem was the the XFS IOLOCK was being held while we waited for > readahead to complete. To fix this, you're planning on waiting for > readahead to complete with the invalidate lock held? I don't see the > benefit. > > I see the invalidate_lock as being roughly equivalent to the IOLOCK, > just pulled up to the VFS. Is that incorrect? > This question coming from you really shakes my confidence. This entire story started from the observation that xfs performance of concurrent mixed rw workload is two orders of magnitude worse than ext4 on slow disk. The reason for the difference was that xfs was taking the IOLOCK shared on reads and ext4 did not. That had two very different reasons: 1. POSIX atomic read/write semantics unique to xfs 2. Correctness w.r.t. races with punch hole etc, which lead to the conclusion that all non-xfs filesystems are buggy in that respect The solution of pulling IOLOCK to vfs would have solved the bug but at the cost of severely regressing the mix rw workload on all fs. The point of Jan's work on invalidate_lock was to fix the bug and avoid the regression. I hope that worked out, but I did not test the mixed rw workload on ext4 after invalidate_lock. IIUC, ideally, invalidate_lock was supposed to be taken only for adding pages to page cache and locking them, but not during IO in order to synchronize against truncating pages (punch hole). But from this comment in filemap_create_folio() I just learned that that is not exactly the case: "...Note that we could release invalidate_lock after inserting the folio into the page cache as the locked folio would then be enough to synchronize with hole punching. But..." Even so, because invalidate_lock is not taken by writers and reader that work on existing pages and because invalidate_lock is not held for the entire read/write operation, statistically it should be less contended than IOLOCK for some workloads, but I am afraid that for the workload I tested (bs=8K and mostly cold page cache) it will be contended with current vfs code. I am going to go find a machine with slow disk to test the random rw workload again on both xfs and ext4 pre and post invalidate_lock and to try out the pre-warm page cache solution. The results could be: a) ext4 random rw performance has been degraded by invalidate_lock b) pre-warm page cache before taking IOLOCK is going to improve xfs random rw performance c) A little bit of both It would be great if you and Jan could agree on the facts and confirm that my observations about invalidate_lock are correct until I get the test results. Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-22 9:00 ` Amir Goldstein @ 2022-06-22 9:34 ` Jan Kara 2022-06-22 16:26 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Jan Kara @ 2022-06-22 9:34 UTC (permalink / raw) To: Amir Goldstein Cc: Matthew Wilcox, Jan Kara, Darrick J . Wong, Dave Chinner, Christoph Hellwig, linux-xfs, linux-fsdevel On Wed 22-06-22 12:00:35, Amir Goldstein wrote: > On Wed, Jun 22, 2022 at 6:23 AM Matthew Wilcox <willy@infradead.org> wrote: > > > > On Tue, Jun 21, 2022 at 03:53:33PM +0300, Amir Goldstein wrote: > > > On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > > > > > > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > > > > How exactly do you imagine the synchronization of buffered read against > > > > > > buffered write would work? Lock all pages for the read range in the page > > > > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > > > > asks to read a huge range... > > > > > > > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > > > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > > > > when reading data into user buffer, but before that, I would like to issue > > > > > and wait for read of the pages in the range to reduce the probability > > > > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > > > > > > > The pre-warm of page cache does not need to abide to the atomic read > > > > > semantics and it is also tolerable if some pages are evicted in between > > > > > pre-warn and read to user buffer - in the worst case this will result in > > > > > I/O amplification, but for the common case, it will be a big win for the > > > > > mixed random r/w performance on xfs. > > > > > > > > > > To reduce risk of page cache thrashing we can limit this optimization > > > > > to a maximum number of page cache pre-warm. > > > > > > > > > > The questions are: > > > > > 1. Does this plan sound reasonable? > > > > > > > > Ah, I see now. So essentially the idea is to pull the readahead (which is > > > > currently happening from filemap_read() -> filemap_get_pages()) out from under > > > > the i_rwsem. It looks like a fine idea to me. > > > > > > Great! > > > Anyone doesn't like the idea or has another suggestion? > > > > I guess I'm still confused. > > > > The problem was the the XFS IOLOCK was being held while we waited for > > readahead to complete. To fix this, you're planning on waiting for > > readahead to complete with the invalidate lock held? I don't see the > > benefit. > > > > I see the invalidate_lock as being roughly equivalent to the IOLOCK, > > just pulled up to the VFS. Is that incorrect? > > > > This question coming from you really shakes my confidence. > > This entire story started from the observation that xfs performance > of concurrent mixed rw workload is two orders of magnitude worse > than ext4 on slow disk. > > The reason for the difference was that xfs was taking the IOLOCK > shared on reads and ext4 did not. > > That had two very different reasons: > 1. POSIX atomic read/write semantics unique to xfs > 2. Correctness w.r.t. races with punch hole etc, which lead to the > conclusion that all non-xfs filesystems are buggy in that respect > > The solution of pulling IOLOCK to vfs would have solved the bug > but at the cost of severely regressing the mix rw workload on all fs. > > The point of Jan's work on invalidate_lock was to fix the bug and > avoid the regression. I hope that worked out, but I did not test > the mixed rw workload on ext4 after invalidate_lock. Yes, it did work out :) > IIUC, ideally, invalidate_lock was supposed to be taken only for > adding pages to page cache and locking them, but not during IO > in order to synchronize against truncating pages (punch hole). > But from this comment in filemap_create_folio() I just learned > that that is not exactly the case: > "...Note that we could release invalidate_lock after inserting the > folio into the page cache as the locked folio would then be enough > to synchronize with hole punching. But..." > > Even so, because invalidate_lock is not taken by writers and reader > that work on existing pages and because invalidate_lock is not held > for the entire read/write operation, statistically it should be less > contended than IOLOCK for some workloads, but I am afraid that > for the workload I tested (bs=8K and mostly cold page cache) it will > be contended with current vfs code. Well, the rules are: When you are adding pages to the page cache you need to either hold i_rwsem or invalidate_lock at least in shared mode. Places removing underlying storage from the page cache pages are responsible for holding both i_rwsem and invalidate_lock in exclusive mode. Writes generally hold i_rwsem exclusive (or shared for overwriting direct IO), reads hold invalidate_lock shared. So there will not be contention on invalidate_lock as such for a mixed rw workload, except for the internal contention of the shared invalidate_lock holders on the cacheline holding the invalidate_lock (which is non-negligible as well in heavily parallel loads but that's a separate story). > I am going to go find a machine with slow disk to test the random rw > workload again on both xfs and ext4 pre and post invalidate_lock and > to try out the pre-warm page cache solution. > > The results could be: > a) ext4 random rw performance has been degraded by invalidate_lock > b) pre-warm page cache before taking IOLOCK is going to improve > xfs random rw performance > c) A little bit of both Well, numbers always beat the theory so I'm all for measuring it but let me say our kernel performance testing within SUSE didn't show significant hit being introduced by invalidate_lock for any major filesystem. I hope this clears out things a bit. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-22 9:34 ` Jan Kara @ 2022-06-22 16:26 ` Amir Goldstein 0 siblings, 0 replies; 41+ messages in thread From: Amir Goldstein @ 2022-06-22 16:26 UTC (permalink / raw) To: Jan Kara Cc: Matthew Wilcox, Darrick J . Wong, Dave Chinner, Christoph Hellwig, linux-xfs, linux-fsdevel > > I am going to go find a machine with slow disk to test the random rw > > workload again on both xfs and ext4 pre and post invalidate_lock and > > to try out the pre-warm page cache solution. > > > > The results could be: > > a) ext4 random rw performance has been degraded by invalidate_lock > > b) pre-warm page cache before taking IOLOCK is going to improve > > xfs random rw performance > > c) A little bit of both The correct answer is b. :) > > Well, numbers always beat the theory so I'm all for measuring it but let me > say our kernel performance testing within SUSE didn't show significant hit > being introduced by invalidate_lock for any major filesystem. > Here are the numbers produced on v5.10.109, on v5.19-rc3 and on v5.19-rc3+ which includes the pre-warn test patch [1]. The numbers are produced by a filebench workload [2] that runs 8 random reader threads and 8 random writer threads for 60 seconds on a cold cache preallocated 5GB file. Note that the machine I tested with has much faster storage than the one that was used 3 years ago, but the performance impact of IOLOCK is still very clear, even larger in this test. If there are no other objections to the pre-warm concept, I will go on to write and test a proper patch. Thanks, Amir. [1] https://github.com/amir73il/linux/commit/70e94f3471739c442b1110ee46e8b59e5d5f5042 [2] https://github.com/amir73il/filebench/blob/overlayfs-devel/workloads/randomrw.f --- EXT4 5.10 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.10.109, ext4 Test #1: rand-write1 3002127ops 50020ops/s 390.8mb/s 0.156ms/op [0.002ms - 213.755ms] rand-read1 31749234ops 528988ops/s 4132.7mb/s 0.010ms/op [0.001ms - 68.884ms] Test #2: rand-write1 3083679ops 51381ops/s 401.4mb/s 0.152ms/op [0.002ms - 181.368ms] rand-read1 32182118ops 536228ops/s 4189.3mb/s 0.010ms/op [0.001ms - 61.158ms] --- EXT4 5.19 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.19-rc3, ext4 Test #1: rand-write1 2829917ops 47159ops/s 368.4mb/s 0.160ms/op [0.002ms - 4709.167ms] rand-read1 36997540ops 616542ops/s 4816.7mb/s 0.009ms/op [0.001ms - 4704.105ms] Test #2: rand-write1 2764486ops 46067ops/s 359.9mb/s 0.170ms/op [0.002ms - 5042.597ms] rand-read1 38893279ops 648118ops/s 5063.4mb/s 0.008ms/op [0.001ms - 5004.069ms] --- XFS 5.10 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.10.109, xfs Test #1: rand-write1 1049278ops 17485ops/s 136.6mb/s 0.456ms/op [0.002ms - 224.062ms] rand-read1 33325ops 555ops/s 4.3mb/s 14.392ms/op [0.007ms - 224.833ms] Test #2: rand-write1 1127497ops 18788ops/s 146.8mb/s 0.424ms/op [0.003ms - 445.810ms] rand-read1 35341ops 589ops/s 4.6mb/s 13.566ms/op [0.005ms - 445.529ms] --- XFS 5.19 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.19-rc3, xfs Test #1: rand-write1 3295934ops 54920ops/s 429.1mb/s 0.144ms/op [0.003ms - 109.703ms] rand-read1 86768ops 1446ops/s 11.3mb/s 5.520ms/op [0.003ms - 372.000ms] Test #2: rand-write1 3246935ops 54106ops/s 422.7mb/s 0.146ms/op [0.002ms - 103.505ms] rand-read1 167018ops 2783ops/s 21.7mb/s 2.867ms/op [0.003ms - 101.105ms] --- XFS+ 5.19 --- filebench randomrw (8 read threads, 8 write threads) kernel 5.19-rc3+ (xfs page cache warmup patch) Test #1: rand-write1 3054567ops 50899ops/s 397.6mb/s 0.154ms/op [0.002ms - 201.531ms] rand-read1 38107333ops 634990ops/s 4960.9mb/s 0.008ms/op [0.001ms - 60.027ms] Test #2: rand-write1 2704416ops 45053ops/s 352.0mb/s 0.174ms/op [0.002ms - 287.079ms] rand-read1 38589737ops 642874ops/s 5022.4mb/s 0.008ms/op [0.001ms - 60.741ms] ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-06-21 12:53 ` Amir Goldstein 2022-06-22 3:23 ` Matthew Wilcox @ 2022-09-13 14:40 ` Amir Goldstein 2022-09-14 16:01 ` Darrick J. Wong 1 sibling, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-09-13 14:40 UTC (permalink / raw) To: Jan Kara, Dave Chinner, Christoph Hellwig Cc: Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Jun 21, 2022 at 3:53 PM Amir Goldstein <amir73il@gmail.com> wrote: > > On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > > How exactly do you imagine the synchronization of buffered read against > > > > buffered write would work? Lock all pages for the read range in the page > > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > > asks to read a huge range... > > > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > > when reading data into user buffer, but before that, I would like to issue > > > and wait for read of the pages in the range to reduce the probability > > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > > > The pre-warm of page cache does not need to abide to the atomic read > > > semantics and it is also tolerable if some pages are evicted in between > > > pre-warn and read to user buffer - in the worst case this will result in > > > I/O amplification, but for the common case, it will be a big win for the > > > mixed random r/w performance on xfs. > > > > > > To reduce risk of page cache thrashing we can limit this optimization > > > to a maximum number of page cache pre-warm. > > > > > > The questions are: > > > 1. Does this plan sound reasonable? > > > > Ah, I see now. So essentially the idea is to pull the readahead (which is > > currently happening from filemap_read() -> filemap_get_pages()) out from under > > the i_rwsem. It looks like a fine idea to me. > Although I was able to demonstrate performance improvement with page cache pre-warming on low latency disks, when testing on a common standard system [*], page cache pre-warming did not yield any improvement to the mixed rw workload. [*] I ran the following fio workload on e2-standard-8 GCE machine: [global] filename=/mnt/xfs/testfile.fio norandommap randrepeat=0 size=5G bs=8K ioengine=psync numjobs=8 group_reporting=1 direct=0 fallocate=1 end_fsync=0 runtime=60 [xfs-read] readwrite=randread [xfs-write] readwrite=randwrite The difference between ext4 and xfs with this machine/workload was two orders of magnitude: root@xfstests:~# fio ./ext4.fio ... Run status group 0 (all jobs): READ: bw=826MiB/s (866MB/s), 826MiB/s-826MiB/s (866MB/s-866MB/s), io=40.0GiB (42.9GB), run=49585-49585msec WRITE: bw=309MiB/s (324MB/s), 309MiB/s-309MiB/s (324MB/s-324MB/s), io=18.1GiB (19.5GB), run=60003-60003msec root@xfstests:~# fio ./xfs.fio ... Run status group 0 (all jobs): READ: bw=7053KiB/s (7223kB/s), 7053KiB/s-7053KiB/s (7223kB/s-7223kB/s), io=413MiB (433MB), run=60007-60007msec WRITE: bw=155MiB/s (163MB/s), 155MiB/s-155MiB/s (163MB/s-163MB/s), io=9324MiB (9777MB), run=60006-60006msec I verified that without XFS_IOLOCK_SHARED xfs fio results are on par with ext4 results for this workload. > > > just cannot comment on whether calling this without i_rwsem does not break > > some internal XFS expectations for stuff like reflink etc. > > relink is done under xfs_ilock2_io_mmap => filemap_invalidate_lock_two > so it should not be a problem. > > pNFS leases I need to look into. > I wonder if xfs_fs_map_blocks() and xfs_fs_commit_blocks() should not be taking the invalidate lock before calling invalidate_inode_pages2() like the xfs callers of truncate_pagecache_range() do? If we do that, then I don't see a problem with buffered read without XFS_IOLOCK_SHARED w.r.t. correctness of layout leases. Dave, Christoph, I know that you said that changing the atomic buffered read semantics is out of the question and that you also objected to a mount option (which nobody will know how to use) and I accept that. Given that a performant range locks implementation is not something trivial to accomplish (Dave please correct me if I am wrong), and given the massive performance impact of XFS_IOLOCK_SHARED on this workload, what do you think about POSIX_FADV_TORN_RW that a specific application can use to opt-out of atomic buffer read semantics? The specific application that I want to modify to use this hint is Samba. Samba uses IO threads by default to issue pread/pwrite on the server for IO requested by the SMB client. The IO size is normally larger than xfs block size and the range may not be block aligned. The SMB protocol has explicit byte range locks and the server implements them, so it is pretty safe to assume that a client that did not request range locks does not need xfs to do the implicit range locking for it. For this reason and because of the huge performance win, I would like to implement POSIX_FADV_TORN_RW in xfs and have Samba try to set this hint when supported. It is very much possible that NFSv4 servers (user and kennel) would also want to set this hint for very similar reasons. Thoughts? Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-13 14:40 ` Amir Goldstein @ 2022-09-14 16:01 ` Darrick J. Wong 2022-09-14 16:29 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Darrick J. Wong @ 2022-09-14 16:01 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Dave Chinner, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Sep 13, 2022 at 05:40:46PM +0300, Amir Goldstein wrote: > On Tue, Jun 21, 2022 at 3:53 PM Amir Goldstein <amir73il@gmail.com> wrote: > > > > On Tue, Jun 21, 2022 at 11:59 AM Jan Kara <jack@suse.cz> wrote: > > > > > > On Tue 21-06-22 10:49:48, Amir Goldstein wrote: > > > > > How exactly do you imagine the synchronization of buffered read against > > > > > buffered write would work? Lock all pages for the read range in the page > > > > > cache? You'd need to be careful to not bring the machine OOM when someone > > > > > asks to read a huge range... > > > > > > > > I imagine that the atomic r/w synchronisation will remain *exactly* as it is > > > > today by taking XFS_IOLOCK_SHARED around generic_file_read_iter(), > > > > when reading data into user buffer, but before that, I would like to issue > > > > and wait for read of the pages in the range to reduce the probability > > > > of doing the read I/O under XFS_IOLOCK_SHARED. > > > > > > > > The pre-warm of page cache does not need to abide to the atomic read > > > > semantics and it is also tolerable if some pages are evicted in between > > > > pre-warn and read to user buffer - in the worst case this will result in > > > > I/O amplification, but for the common case, it will be a big win for the > > > > mixed random r/w performance on xfs. > > > > > > > > To reduce risk of page cache thrashing we can limit this optimization > > > > to a maximum number of page cache pre-warm. > > > > > > > > The questions are: > > > > 1. Does this plan sound reasonable? > > > > > > Ah, I see now. So essentially the idea is to pull the readahead (which is > > > currently happening from filemap_read() -> filemap_get_pages()) out from under > > > the i_rwsem. It looks like a fine idea to me. > > > > Although I was able to demonstrate performance improvement > with page cache pre-warming on low latency disks, when testing > on a common standard system [*], page cache pre-warming did not > yield any improvement to the mixed rw workload. > > [*] I ran the following fio workload on e2-standard-8 GCE machine: > > [global] > filename=/mnt/xfs/testfile.fio > norandommap > randrepeat=0 > size=5G > bs=8K > ioengine=psync > numjobs=8 > group_reporting=1 > direct=0 > fallocate=1 > end_fsync=0 > runtime=60 > > [xfs-read] > readwrite=randread > > [xfs-write] > readwrite=randwrite > > The difference between ext4 and xfs with this machine/workload was > two orders of magnitude: > > root@xfstests:~# fio ./ext4.fio > ... > Run status group 0 (all jobs): > READ: bw=826MiB/s (866MB/s), 826MiB/s-826MiB/s (866MB/s-866MB/s), > io=40.0GiB (42.9GB), run=49585-49585msec > WRITE: bw=309MiB/s (324MB/s), 309MiB/s-309MiB/s (324MB/s-324MB/s), > io=18.1GiB (19.5GB), run=60003-60003msec > > root@xfstests:~# fio ./xfs.fio > ... > Run status group 0 (all jobs): > READ: bw=7053KiB/s (7223kB/s), 7053KiB/s-7053KiB/s > (7223kB/s-7223kB/s), io=413MiB (433MB), run=60007-60007msec > WRITE: bw=155MiB/s (163MB/s), 155MiB/s-155MiB/s (163MB/s-163MB/s), > io=9324MiB (9777MB), run=60006-60006msec > > I verified that without XFS_IOLOCK_SHARED xfs fio results are on par > with ext4 results for this workload. > > > > > > just cannot comment on whether calling this without i_rwsem does not break > > > some internal XFS expectations for stuff like reflink etc. > > > > relink is done under xfs_ilock2_io_mmap => filemap_invalidate_lock_two > > so it should not be a problem. > > > > pNFS leases I need to look into. > > > > I wonder if xfs_fs_map_blocks() and xfs_fs_commit_blocks() > should not be taking the invalidate lock before calling > invalidate_inode_pages2() like the xfs callers of > truncate_pagecache_range() do? > > If we do that, then I don't see a problem with buffered read > without XFS_IOLOCK_SHARED w.r.t. correctness of layout leases. > > Dave, Christoph, > > I know that you said that changing the atomic buffered read semantics > is out of the question and that you also objected to a mount option > (which nobody will know how to use) and I accept that. > > Given that a performant range locks implementation is not something > trivial to accomplish (Dave please correct me if I am wrong), > and given the massive performance impact of XFS_IOLOCK_SHARED > on this workload, > what do you think about POSIX_FADV_TORN_RW that a specific > application can use to opt-out of atomic buffer read semantics? > > The specific application that I want to modify to use this hint is Samba. > Samba uses IO threads by default to issue pread/pwrite on the server > for IO requested by the SMB client. The IO size is normally larger than > xfs block size and the range may not be block aligned. > > The SMB protocol has explicit byte range locks and the server implements > them, so it is pretty safe to assume that a client that did not request > range locks does not need xfs to do the implicit range locking for it. > > For this reason and because of the huge performance win, > I would like to implement POSIX_FADV_TORN_RW in xfs and > have Samba try to set this hint when supported. > > It is very much possible that NFSv4 servers (user and kennel) > would also want to set this hint for very similar reasons. > > Thoughts? How about range locks for i_rwsem and invalidate_lock? That could reduce contention on VM farms, though I can only assume that, given that I don't have a reference implementation to play with... --D > Thanks, > Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-14 16:01 ` Darrick J. Wong @ 2022-09-14 16:29 ` Amir Goldstein 2022-09-14 17:39 ` Darrick J. Wong 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-09-14 16:29 UTC (permalink / raw) To: Darrick J. Wong Cc: Jan Kara, Dave Chinner, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel > > Dave, Christoph, > > > > I know that you said that changing the atomic buffered read semantics > > is out of the question and that you also objected to a mount option > > (which nobody will know how to use) and I accept that. > > > > Given that a performant range locks implementation is not something > > trivial to accomplish (Dave please correct me if I am wrong), > > and given the massive performance impact of XFS_IOLOCK_SHARED > > on this workload, > > what do you think about POSIX_FADV_TORN_RW that a specific > > application can use to opt-out of atomic buffer read semantics? > > > > The specific application that I want to modify to use this hint is Samba. > > Samba uses IO threads by default to issue pread/pwrite on the server > > for IO requested by the SMB client. The IO size is normally larger than > > xfs block size and the range may not be block aligned. > > > > The SMB protocol has explicit byte range locks and the server implements > > them, so it is pretty safe to assume that a client that did not request > > range locks does not need xfs to do the implicit range locking for it. > > > > For this reason and because of the huge performance win, > > I would like to implement POSIX_FADV_TORN_RW in xfs and > > have Samba try to set this hint when supported. > > > > It is very much possible that NFSv4 servers (user and kennel) > > would also want to set this hint for very similar reasons. > > > > Thoughts? > > How about range locks for i_rwsem and invalidate_lock? That could > reduce contention on VM farms, though I can only assume that, given that > I don't have a reference implementation to play with... > If you are asking if I have the bandwidth to work on range lock then the answer is that I do not. IIRC, Dave had a WIP and ran some benchmarks with range locks, but I do not know at which state that work is. The question is, if application developers know (or believe) that their application does not care about torn reads, are we insisting not to allow them to opt out of atomic buffered reads (which they do not need) because noone has the time to work on range locks? If that is the final decision then if customers come to me to complain about this workload, my response will be: If this workload is important for your application, either - contribute developer resource to work on range locks - carry a patch in your kernel or - switch to another filesystem for this workload Thanks, Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-14 16:29 ` Amir Goldstein @ 2022-09-14 17:39 ` Darrick J. Wong 2022-09-19 23:09 ` Dave Chinner 0 siblings, 1 reply; 41+ messages in thread From: Darrick J. Wong @ 2022-09-14 17:39 UTC (permalink / raw) To: Amir Goldstein Cc: Jan Kara, Dave Chinner, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Wed, Sep 14, 2022 at 07:29:15PM +0300, Amir Goldstein wrote: > > > Dave, Christoph, > > > > > > I know that you said that changing the atomic buffered read semantics > > > is out of the question and that you also objected to a mount option > > > (which nobody will know how to use) and I accept that. > > > > > > Given that a performant range locks implementation is not something > > > trivial to accomplish (Dave please correct me if I am wrong), > > > and given the massive performance impact of XFS_IOLOCK_SHARED > > > on this workload, > > > what do you think about POSIX_FADV_TORN_RW that a specific > > > application can use to opt-out of atomic buffer read semantics? > > > > > > The specific application that I want to modify to use this hint is Samba. > > > Samba uses IO threads by default to issue pread/pwrite on the server > > > for IO requested by the SMB client. The IO size is normally larger than > > > xfs block size and the range may not be block aligned. > > > > > > The SMB protocol has explicit byte range locks and the server implements > > > them, so it is pretty safe to assume that a client that did not request > > > range locks does not need xfs to do the implicit range locking for it. > > > > > > For this reason and because of the huge performance win, > > > I would like to implement POSIX_FADV_TORN_RW in xfs and > > > have Samba try to set this hint when supported. > > > > > > It is very much possible that NFSv4 servers (user and kennel) > > > would also want to set this hint for very similar reasons. > > > > > > Thoughts? > > > > How about range locks for i_rwsem and invalidate_lock? That could > > reduce contention on VM farms, though I can only assume that, given that > > I don't have a reference implementation to play with... > > > > If you are asking if I have the bandwidth to work on range lock > then the answer is that I do not. > > IIRC, Dave had a WIP and ran some benchmarks with range locks, > but I do not know at which state that work is. Yeah, that's what I was getting at -- I really wish Dave would post that as an RFC. The last time I talked to him about it, he was worried that the extra complexity of the range lock structure would lead to more memory traffic and overhead. I /know/ there are a lot of cloud vendors that would appreciate the speedup that range locking might provide. I'm also fairly sure there are also people who want maximum single threaded iops and will /not/ like range locks, but I think we ought to let kernel distributors choose which one they want. Recently I've been playing around with static keys, because certain parts of xfs online fsck need to hook into libxfs. The hooks have some overhead, so I'd want to reduce the cost of that to making the instruction prefetcher skip over a nop sled when fsck isn't running. I sorta suspect this is a way out -- the distributor selects a default locking implementation at kbuild time, and we allow a kernel command line parameter to switch (if desired) during early boot. That only works if the compiler supports asm goto (iirc) but that's not /so/ uncommon. I'll try to prod Dave about this later today, maybe we can find someone to work on it if he'd post the prototype. --D > The question is, if application developers know (or believe) > that their application does not care about torn reads, are we > insisting not to allow them to opt out of atomic buffered reads > (which they do not need) because noone has the time to > work on range locks? > > If that is the final decision then if customers come to me to > complain about this workload, my response will be: > > If this workload is important for your application, either > - contribute developer resource to work on range locks > - carry a patch in your kernel > or > - switch to another filesystem for this workload > > Thanks, > Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-14 17:39 ` Darrick J. Wong @ 2022-09-19 23:09 ` Dave Chinner 2022-09-20 2:24 ` Dave Chinner 0 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2022-09-19 23:09 UTC (permalink / raw) To: Darrick J. Wong Cc: Amir Goldstein, Jan Kara, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Wed, Sep 14, 2022 at 10:39:45AM -0700, Darrick J. Wong wrote: > On Wed, Sep 14, 2022 at 07:29:15PM +0300, Amir Goldstein wrote: > > > > Dave, Christoph, > > > > > > > > I know that you said that changing the atomic buffered read semantics > > > > is out of the question and that you also objected to a mount option > > > > (which nobody will know how to use) and I accept that. > > > > > > > > Given that a performant range locks implementation is not something > > > > trivial to accomplish (Dave please correct me if I am wrong), > > > > and given the massive performance impact of XFS_IOLOCK_SHARED > > > > on this workload, > > > > what do you think about POSIX_FADV_TORN_RW that a specific > > > > application can use to opt-out of atomic buffer read semantics? > > > > > > > > The specific application that I want to modify to use this hint is Samba. > > > > Samba uses IO threads by default to issue pread/pwrite on the server > > > > for IO requested by the SMB client. The IO size is normally larger than > > > > xfs block size and the range may not be block aligned. > > > > > > > > The SMB protocol has explicit byte range locks and the server implements > > > > them, so it is pretty safe to assume that a client that did not request > > > > range locks does not need xfs to do the implicit range locking for it. > > > > > > > > For this reason and because of the huge performance win, > > > > I would like to implement POSIX_FADV_TORN_RW in xfs and > > > > have Samba try to set this hint when supported. > > > > > > > > It is very much possible that NFSv4 servers (user and kennel) > > > > would also want to set this hint for very similar reasons. > > > > > > > > Thoughts? > > > > > > How about range locks for i_rwsem and invalidate_lock? That could > > > reduce contention on VM farms, though I can only assume that, given that > > > I don't have a reference implementation to play with... > > > > > > > If you are asking if I have the bandwidth to work on range lock > > then the answer is that I do not. > > > > IIRC, Dave had a WIP and ran some benchmarks with range locks, > > but I do not know at which state that work is. > > Yeah, that's what I was getting at -- I really wish Dave would post that > as an RFC. The last time I talked to him about it, he was worried that > the extra complexity of the range lock structure would lead to more > memory traffic and overhead. The reason I haven't posted it is that I don't think range locks can ever be made to perform and scale as we need for the IO path. The problem with range locks is that the structure that tracks the locked ranges needs locking itself, and that means taking an IO lock is no longer just a single atomic operation - it's at least two atomic ops (lock, unlock on a spin lock) and then a bunch of cache misses while searching up the structure containing the range locks looking for overlaps. Hence a { range_lock(); range_unlock(); } pair is at minimum twice as costly { down_read(); up_read(); } and that shows up dramatically with direct IO. My test system (2s, 32p) handles about 3 million atomic ops for a single cacheline across many CPUs before it breaks down into cacheline contention and goes really slow. That means I can run 1.6 million read/write DIO iops to a single file on the test machine with shared rwsem locking (~3.2 million atomic ops a second) but with range locks (assuming just atomic op overhead) that drops to ~800k r/w DIO ops. The hardware IO capacity is just over 1.7MIOPS... In reality, this contended cacheline is not the limiting factor for range locks - the limiting factor is the time it takes to run the critical section inside that lock. This was found with the mmap_sem when it was converted to range locks - the cache misses doing rb-tree pointer chasing with the spinlock held meant that the actual range lock rate topped out at about 180k lock,unlock pairs per second. i.e. an order of magnitude slower than a rwsem on this machine. Read this thread again: https://lore.kernel.org/linux-xfs/20190416122240.GN29573@dread.disaster.area/ That's really the elephant in the range locking room: a range lock with a locked search and update aglorithm can't scale beyond a single CPU in it's critical section. It's a hard limit no matter how many CPUs you have and how much concurrency the workload has - the range lock has a single threaded critical section that results in a hard computational limit on range lock operations. Hence I was looking at using a novel OLC btree algorithm for storing the range locks. The RCU-based OLC btree is largely lockless, allowing conconcurrent search, insert and delete operations on range based index. I've largely got the OLC btree to work, but that simply exposed a further problem that range locks need to handle. That is, the biggest problem for scaling range lock performance is that locking is mostly singleton operation - very few workloads actually use concurrent access to a single file and hence need multiple range locks held at once. As a result, the typical concurrent IO range lock workload results in a single node btree, and so all lookups, inserts and remove hammer the seqlocks on a single node and we end up contending on a single cache line again. Comared to a rwsem, we consume a lot more CPU overhead before we detect a change has occurred and we need to go around and try again. That said, it's better than previous range lock implementations in that it gets up to about 400-450k mixed DIO and buffered iops, but it is still way, way down on using a shared rwsem or serialising at a page granularity via page locks. Yes, I know there are many advantages to range locking. Because we can exclude specific ranges, operations like truncate, fallocate, buffered writes, etc can all run concurrently with reads. DIO can run perfectly coherently with buffered IO (mmap is still a problem!). We can extend files without having to serialise against other IO within the existing EOF. We can pass lock contexts with AIO so that the inode can be unlocked at completion and we can get rid of the nasty inode_dio_wait() stuff we have for synchronisation with DIO. And so on. IOWs, while there are many upsides to range locking the reality is that single file IO performance will not scale to storage hardware capability any more. I have few thoughts on how range locking could be further optimised to avoid such overheads in the cases where range locking is not necessary, but I really don't think that the scalability of a range lock will ever be sufficient to allow us to track every IO we have in flight. > I /know/ there are a lot of cloud vendors that would appreciate the > speedup that range locking might provide. I'm also fairly sure there > are also people who want maximum single threaded iops and will /not/ > like range locks, but I think we ought to let kernel distributors choose > which one they want. Speedup for what operations? Not single file DIO, and only for mixed buffered read/write. Perhaps for mixed fallocate/DIO workloads might benefit, but I reluctantly came to the conclusion that there really aren't many workloads that even a highly optimised rangelock would actually end up improving performance for... > Recently I've been playing around with static keys, because certain > parts of xfs online fsck need to hook into libxfs. The hooks have some > overhead, so I'd want to reduce the cost of that to making the > instruction prefetcher skip over a nop sled when fsck isn't running. > I sorta suspect this is a way out -- the distributor selects a default > locking implementation at kbuild time, and we allow a kernel command > line parameter to switch (if desired) during early boot. That only > works if the compiler supports asm goto (iirc) but that's not /so/ > uncommon. I think it's a lot harder than that. The range lock requires a signification on-stack structure to be declared in the context that the lock is being taken. i.e.: +#define RANGE_LOCK_FULL (LLONG_MAX) + +struct range_lock { + uint64_t start; + uint64_t end; + struct list_head wait_list; +#ifdef __KERNEL__ + struct task_struct *task; +#else + pthread_cond_t task; +#endif +}; + +#define __RANGE_LOCK_INITIALIZER(__name, __start, __end) { \ + .start = (__start) \ + ,.end = (__end) \ + ,.wait_list = LIST_HEAD_INIT((__name).wait_list) \ + } + +#define DEFINE_RANGE_LOCK(name, start, end) \ + struct range_lock name = __RANGE_LOCK_INITIALIZER((name), (start), (end)) + +#define DEFINE_RANGE_LOCK_FULL(name) \ + struct range_lock name = __RANGE_LOCK_INITIALIZER((name), 0, RANGE_LOCK_FULL) And code that uses it looks like: +static inline void +xfs_iolock_range_init( + struct xfs_inode *ip, + struct range_lock *rlock, + uint64_t start, + uint64_t count) +{ + int rounding; + + rounding = max_t(int, i_blocksize(VFS_I(ip)), PAGE_SIZE); + range_lock_init(rlock, round_down(start, rounding), + round_up(start + count, rounding)); +} + STATIC ssize_t xfs_file_dio_read( struct kiocb *iocb, struct iov_iter *to) { struct xfs_inode *ip = XFS_I(file_inode(iocb->ki_filp)); + size_t count = iov_iter_count(to); ssize_t ret; + struct range_lock rlock; trace_xfs_file_direct_read(iocb, to); - if (!iov_iter_count(to)) + if (!count) return 0; /* skip atime */ file_accessed(iocb->ki_filp); - ret = xfs_ilock_iocb(iocb, XFS_VFSLOCK_SHARED); + xfs_iolock_range_init(ip, &rlock, iocb->ki_pos, count); + ret = xfs_ilock_iocb(iocb, &rlock, XFS_VFSLOCK_SHARED); Hence I don't think this is as simple as using static keys to switch code paths as there's a whole lot more information that needs to be set up for range locks compared to just using rwsems.... -Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-19 23:09 ` Dave Chinner @ 2022-09-20 2:24 ` Dave Chinner 2022-09-20 3:08 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2022-09-20 2:24 UTC (permalink / raw) To: Darrick J. Wong Cc: Amir Goldstein, Jan Kara, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Sep 20, 2022 at 09:09:47AM +1000, Dave Chinner wrote: > On Wed, Sep 14, 2022 at 10:39:45AM -0700, Darrick J. Wong wrote: > > On Wed, Sep 14, 2022 at 07:29:15PM +0300, Amir Goldstein wrote: > > > > > Dave, Christoph, > > > > > > > > > > I know that you said that changing the atomic buffered read semantics > > > > > is out of the question and that you also objected to a mount option > > > > > (which nobody will know how to use) and I accept that. > > > > > > > > > > Given that a performant range locks implementation is not something > > > > > trivial to accomplish (Dave please correct me if I am wrong), > > > > > and given the massive performance impact of XFS_IOLOCK_SHARED > > > > > on this workload, > > > > > what do you think about POSIX_FADV_TORN_RW that a specific > > > > > application can use to opt-out of atomic buffer read semantics? > > > > > > > > > > The specific application that I want to modify to use this hint is Samba. > > > > > Samba uses IO threads by default to issue pread/pwrite on the server > > > > > for IO requested by the SMB client. The IO size is normally larger than > > > > > xfs block size and the range may not be block aligned. > > > > > > > > > > The SMB protocol has explicit byte range locks and the server implements > > > > > them, so it is pretty safe to assume that a client that did not request > > > > > range locks does not need xfs to do the implicit range locking for it. That doesn't cover concurrent local (server side) access to the file. It's not uncommon to have the same filesystems exported by both Samba and NFS at the same time, and the only point of co-ordination between the two is the underlying local filesystem.... IOWs, when we are talking about local filesystem behaviour, what a network protocol does above the filesystem is largely irrelevant to the synchronisation required within the filesystem implementation.... > > > > > For this reason and because of the huge performance win, > > > > > I would like to implement POSIX_FADV_TORN_RW in xfs and > > > > > have Samba try to set this hint when supported. > > > > > > > > > > It is very much possible that NFSv4 servers (user and kennel) > > > > > would also want to set this hint for very similar reasons. > > > > > > > > > > Thoughts? > > > > > > > > How about range locks for i_rwsem and invalidate_lock? That could > > > > reduce contention on VM farms, though I can only assume that, given that > > > > I don't have a reference implementation to play with... > > > > > > > > > > If you are asking if I have the bandwidth to work on range lock > > > then the answer is that I do not. > > > > > > IIRC, Dave had a WIP and ran some benchmarks with range locks, > > > but I do not know at which state that work is. > > > > Yeah, that's what I was getting at -- I really wish Dave would post that > > as an RFC. The last time I talked to him about it, he was worried that > > the extra complexity of the range lock structure would lead to more > > memory traffic and overhead. > > The reason I haven't posted it is that I don't think range locks can > ever be made to perform and scale as we need for the IO path. [snip range lock scalability and perf issues] As I just discussed on #xfs with Darrick, there are other options we can persue here. The first question we need to ask ourselves is this: what are we protecting against with exclusive buffered write behaviour? The answer is that we know there are custom enterprise database applications out there that assume that 8-16kB buffered writes are atomic. I wish I could say these are legacy applications these days, but they aren't - they are still in production use, and the applications build on those custom database engines are still under active development and use. AFAIK, the 8kB atomic write behaviour is historical and came from applications originally designed for Solaris and hardware that had an 8kB page size. Hence buffered 8kB writes were assumed to be the largest atomic write size that concurrent reads would not see write tearing. These applications are now run on x86-64 boxes with 4kB page size, but they still assume that 8kB writes are atomic and can't tear. So, really, these days the atomic write behaviour of XFS is catering for these small random read/write IO applications, not to provide atomic writes for bulk data moving applications writing 2GB of data per write() syscall. Hence we can fairly safely say that we really only need "exclusive" buffered write locking for relatively small multipage IOs, not huge IOs. We can do single page shared buffered writes immediately - we guarantee that while the folio is locked, a buffered read cannot access the data until the folio is unlocked. So that could be the first step to relaxing the exclusive locking requirement for buffered writes. Next we need to consider that we now have large folio support in the page cache, which means we can treat contiguous file ranges larger than a single page a single atomic unit if they are covered by a multi-page folio. As such, if we have a single multi-page folio that spans the entire write() range already in cache, we can run that write atomically under a shared IO lock the same as we can do with single page folios. However, what happens if the folio is smaller than the range we need to write? Well, in that case, we have to abort the shared lock write and upgrade to an exclusive lock before trying again. Of course, we can only determine if the write can go ahead once we have the folio locked. That means we need a new non-blocking write condition to be handled by the iomap code. We already have several of them because of IOCB_NOWAIT semantics that io_uring requires for buffered writes, so we are already well down the path of needing to support fully non-blocking writes through iomap. Further, the recent concurrent write data corruption that we uncovered requires a new hook in the iomap write path to allow writes to be aborted for remapping because the cached iomap has become stale. This validity check can only be done once the folio has locked - if the cached iomap is stale once we have the page locked, then we have to back out and remap the write range and re-run the write. IOWs, we are going to have to add write retries to the iomap write path for data integrity purposes. These checks must be done only after the folio has been locked, so we really end up getting the "can't do atomic write" retry infrastructure for free with the data corruption fixes... With this in place, it becomes trivial to support atomic writes with shared locking all the way up to PMD sizes (or whatever the maximum multipage folio size the arch supports is) with a minimal amount of extra code. At this point, we have a buffered write path that tries to do shared locking first, and only falls back to exclusive locking if the page cache doesn't contain a folio large enough to soak up the entire write. In future, Darrick suggested we might be able to do a "trygetlock a bunch of folios" operation that locks a range of folios within the current iomap in one go, and then we write into all of them in a batch before unlocking them all. This would give us multi-folio atomic writes with shared locking - this is much more complex, and it's unclear that multi-folio write batching will gain us anything over the single folio check described above... Finally, for anything that is concurrently reading and writing lots of data in chunks larger than PMD sizes, the application should really be using DIO with AIO or io_uring. So falling back to exclusive locking for such large single buffered write IOs doesn't seem like a huge issue right now.... Thoughts? -Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-20 2:24 ` Dave Chinner @ 2022-09-20 3:08 ` Amir Goldstein 2022-09-21 11:20 ` Amir Goldstein 0 siblings, 1 reply; 41+ messages in thread From: Amir Goldstein @ 2022-09-20 3:08 UTC (permalink / raw) To: Dave Chinner Cc: Darrick J. Wong, Jan Kara, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Sep 20, 2022 at 5:24 AM Dave Chinner <david@fromorbit.com> wrote: > > On Tue, Sep 20, 2022 at 09:09:47AM +1000, Dave Chinner wrote: > > On Wed, Sep 14, 2022 at 10:39:45AM -0700, Darrick J. Wong wrote: > > > On Wed, Sep 14, 2022 at 07:29:15PM +0300, Amir Goldstein wrote: > > > > > > Dave, Christoph, > > > > > > > > > > > > I know that you said that changing the atomic buffered read semantics > > > > > > is out of the question and that you also objected to a mount option > > > > > > (which nobody will know how to use) and I accept that. > > > > > > > > > > > > Given that a performant range locks implementation is not something > > > > > > trivial to accomplish (Dave please correct me if I am wrong), > > > > > > and given the massive performance impact of XFS_IOLOCK_SHARED > > > > > > on this workload, > > > > > > what do you think about POSIX_FADV_TORN_RW that a specific > > > > > > application can use to opt-out of atomic buffer read semantics? > > > > > > > > > > > > The specific application that I want to modify to use this hint is Samba. > > > > > > Samba uses IO threads by default to issue pread/pwrite on the server > > > > > > for IO requested by the SMB client. The IO size is normally larger than > > > > > > xfs block size and the range may not be block aligned. > > > > > > > > > > > > The SMB protocol has explicit byte range locks and the server implements > > > > > > them, so it is pretty safe to assume that a client that did not request > > > > > > range locks does not need xfs to do the implicit range locking for it. > > That doesn't cover concurrent local (server side) access to the > file. It's not uncommon to have the same filesystems exported by > both Samba and NFS at the same time, and the only point of > co-ordination between the two is the underlying local filesystem.... > > IOWs, when we are talking about local filesystem behaviour, what a > network protocol does above the filesystem is largely irrelevant to > the synchronisation required within the filesystem > implementation.... > Perhaps I did not explain my proposal well. Maybe I should have named it POSIX_FADV_TORN_READ. The fadvise() from nfs/smb server would affect only the behavior of buffered reads on the open fd of that server, it will not affect any buffered IO on that inode not associated with the application that opted-in to this behavior. Also, the nfs/smb server buffered writes are still under the same exclusive IO lock as the rest of the callers. > > > > > > For this reason and because of the huge performance win, > > > > > > I would like to implement POSIX_FADV_TORN_RW in xfs and > > > > > > have Samba try to set this hint when supported. > > > > > > > > > > > > It is very much possible that NFSv4 servers (user and kennel) > > > > > > would also want to set this hint for very similar reasons. > > > > > > > > > > > > Thoughts? > > > > > > > > > > How about range locks for i_rwsem and invalidate_lock? That could > > > > > reduce contention on VM farms, though I can only assume that, given that > > > > > I don't have a reference implementation to play with... > > > > > > > > > > > > > If you are asking if I have the bandwidth to work on range lock > > > > then the answer is that I do not. > > > > > > > > IIRC, Dave had a WIP and ran some benchmarks with range locks, > > > > but I do not know at which state that work is. > > > > > > Yeah, that's what I was getting at -- I really wish Dave would post that > > > as an RFC. The last time I talked to him about it, he was worried that > > > the extra complexity of the range lock structure would lead to more > > > memory traffic and overhead. > > > > The reason I haven't posted it is that I don't think range locks can > > ever be made to perform and scale as we need for the IO path. > > [snip range lock scalability and perf issues] > > As I just discussed on #xfs with Darrick, there are other options > we can persue here. > > The first question we need to ask ourselves is this: what are we > protecting against with exclusive buffered write behaviour? > > The answer is that we know there are custom enterprise database > applications out there that assume that 8-16kB buffered writes are > atomic. I wish I could say these are legacy applications these days, > but they aren't - they are still in production use, and the > applications build on those custom database engines are still under > active development and use. > > AFAIK, the 8kB atomic write behaviour is historical and came from > applications originally designed for Solaris and hardware that > had an 8kB page size. Hence buffered 8kB writes were assumed to be > the largest atomic write size that concurrent reads would not see > write tearing. These applications are now run on x86-64 boxes with > 4kB page size, but they still assume that 8kB writes are atomic and > can't tear. > Interesting. I did not know which applications needed that behavior. The customer benchmark that started the complaint uses 8k buffered IO size (as do the benchmarks that I posted in this thread), so far as I am concerned, fixing small buffered IO will solve the problem. > So, really, these days the atomic write behaviour of XFS is catering > for these small random read/write IO applications, not to provide > atomic writes for bulk data moving applications writing 2GB of data > per write() syscall. Hence we can fairly safely say that we really > only need "exclusive" buffered write locking for relatively small > multipage IOs, not huge IOs. > > We can do single page shared buffered writes immediately - we > guarantee that while the folio is locked, a buffered read cannot > access the data until the folio is unlocked. So that could be the > first step to relaxing the exclusive locking requirement for > buffered writes. > > Next we need to consider that we now have large folio support in the > page cache, which means we can treat contiguous file ranges larger > than a single page a single atomic unit if they are covered by a > multi-page folio. As such, if we have a single multi-page folio that > spans the entire write() range already in cache, we can run that > write atomically under a shared IO lock the same as we can do with > single page folios. > > However, what happens if the folio is smaller than the range we need > to write? Well, in that case, we have to abort the shared lock write > and upgrade to an exclusive lock before trying again. > > Of course, we can only determine if the write can go ahead once we > have the folio locked. That means we need a new non-blocking write > condition to be handled by the iomap code. We already have several > of them because of IOCB_NOWAIT semantics that io_uring requires for > buffered writes, so we are already well down the path of needing to > support fully non-blocking writes through iomap. > > Further, the recent concurrent write data corruption that we > uncovered requires a new hook in the iomap write path to allow > writes to be aborted for remapping because the cached iomap has > become stale. This validity check can only be done once the folio > has locked - if the cached iomap is stale once we have the page > locked, then we have to back out and remap the write range and > re-run the write. > > IOWs, we are going to have to add write retries to the iomap write > path for data integrity purposes. These checks must be done only > after the folio has been locked, so we really end up getting the > "can't do atomic write" retry infrastructure for free with the data > corruption fixes... > > With this in place, it becomes trivial to support atomic writes with > shared locking all the way up to PMD sizes (or whatever the maximum > multipage folio size the arch supports is) with a minimal amount of > extra code. > > At this point, we have a buffered write path that tries to do shared > locking first, and only falls back to exclusive locking if the page > cache doesn't contain a folio large enough to soak up the entire > write. > > In future, Darrick suggested we might be able to do a "trygetlock a > bunch of folios" operation that locks a range of folios within the > current iomap in one go, and then we write into all of them in a > batch before unlocking them all. This would give us multi-folio > atomic writes with shared locking - this is much more complex, and > it's unclear that multi-folio write batching will gain us anything > over the single folio check described above... > > Finally, for anything that is concurrently reading and writing lots > of data in chunks larger than PMD sizes, the application should > really be using DIO with AIO or io_uring. So falling back to > exclusive locking for such large single buffered write IOs doesn't > seem like a huge issue right now.... > > Thoughts? That sounds like a great plan. I especially liked the "get it for free" part ;) Is there already WIP for the data integrity issue fix? If there is anything I can do to assist, run the benchmark or anything please let me know. In the meanwhile, I will run the benchmark with XFS_IOLOCK_SHARED on the write() path. Thanks! Amir. ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2022-09-20 3:08 ` Amir Goldstein @ 2022-09-21 11:20 ` Amir Goldstein 0 siblings, 0 replies; 41+ messages in thread From: Amir Goldstein @ 2022-09-21 11:20 UTC (permalink / raw) To: Dave Chinner Cc: Darrick J. Wong, Jan Kara, Christoph Hellwig, Darrick J . Wong, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Sep 20, 2022 at 6:08 AM Amir Goldstein <amir73il@gmail.com> wrote: > [...] > > As I just discussed on #xfs with Darrick, there are other options > > we can persue here. > > > > The first question we need to ask ourselves is this: what are we > > protecting against with exclusive buffered write behaviour? > > > > The answer is that we know there are custom enterprise database > > applications out there that assume that 8-16kB buffered writes are > > atomic. I wish I could say these are legacy applications these days, > > but they aren't - they are still in production use, and the > > applications build on those custom database engines are still under > > active development and use. > > > > AFAIK, the 8kB atomic write behaviour is historical and came from > > applications originally designed for Solaris and hardware that > > had an 8kB page size. Hence buffered 8kB writes were assumed to be > > the largest atomic write size that concurrent reads would not see > > write tearing. These applications are now run on x86-64 boxes with > > 4kB page size, but they still assume that 8kB writes are atomic and > > can't tear. > > > > Interesting. I did not know which applications needed that behavior. > The customer benchmark that started the complaint uses 8k buffered > IO size (as do the benchmarks that I posted in this thread), so far as > I am concerned, fixing small buffered IO will solve the problem. > > > So, really, these days the atomic write behaviour of XFS is catering > > for these small random read/write IO applications, not to provide > > atomic writes for bulk data moving applications writing 2GB of data > > per write() syscall. Hence we can fairly safely say that we really > > only need "exclusive" buffered write locking for relatively small > > multipage IOs, not huge IOs. > > > > We can do single page shared buffered writes immediately - we > > guarantee that while the folio is locked, a buffered read cannot > > access the data until the folio is unlocked. So that could be the > > first step to relaxing the exclusive locking requirement for > > buffered writes. > > > > Next we need to consider that we now have large folio support in the > > page cache, which means we can treat contiguous file ranges larger > > than a single page a single atomic unit if they are covered by a > > multi-page folio. As such, if we have a single multi-page folio that > > spans the entire write() range already in cache, we can run that > > write atomically under a shared IO lock the same as we can do with > > single page folios. > > > > However, what happens if the folio is smaller than the range we need > > to write? Well, in that case, we have to abort the shared lock write > > and upgrade to an exclusive lock before trying again. > > Please correct me if I am wrong, but with current upstream, the only way that multi page folios are created for 4K block / 4K page setup are during readahead. We *could* allocate multi page folios on write to an allocated block range that maps inside a single extent, but there is no code for that today. It seems that without this code, any write to a region of page cache not pre-populated using readahead, would get exclusive iolock for 8K buffered writes until that single page folio cache entry is evicted. Am I reading the iomap code correctly? > > Of course, we can only determine if the write can go ahead once we > > have the folio locked. That means we need a new non-blocking write > > condition to be handled by the iomap code. We already have several > > of them because of IOCB_NOWAIT semantics that io_uring requires for > > buffered writes, so we are already well down the path of needing to > > support fully non-blocking writes through iomap. > > > > Further, the recent concurrent write data corruption that we > > uncovered requires a new hook in the iomap write path to allow > > writes to be aborted for remapping because the cached iomap has > > become stale. This validity check can only be done once the folio > > has locked - if the cached iomap is stale once we have the page > > locked, then we have to back out and remap the write range and > > re-run the write. > > > > IOWs, we are going to have to add write retries to the iomap write > > path for data integrity purposes. These checks must be done only > > after the folio has been locked, so we really end up getting the > > "can't do atomic write" retry infrastructure for free with the data > > corruption fixes... > > > > With this in place, it becomes trivial to support atomic writes with > > shared locking all the way up to PMD sizes (or whatever the maximum > > multipage folio size the arch supports is) with a minimal amount of > > extra code. > > > > At this point, we have a buffered write path that tries to do shared > > locking first, and only falls back to exclusive locking if the page > > cache doesn't contain a folio large enough to soak up the entire > > write. > > > > In future, Darrick suggested we might be able to do a "trygetlock a > > bunch of folios" operation that locks a range of folios within the > > current iomap in one go, and then we write into all of them in a > > batch before unlocking them all. This would give us multi-folio > > atomic writes with shared locking - this is much more complex, and > > it's unclear that multi-folio write batching will gain us anything > > over the single folio check described above... > > > > Finally, for anything that is concurrently reading and writing lots > > of data in chunks larger than PMD sizes, the application should > > really be using DIO with AIO or io_uring. So falling back to > > exclusive locking for such large single buffered write IOs doesn't > > seem like a huge issue right now.... > > > > Thoughts? > > That sounds like a great plan. > I especially liked the "get it for free" part ;) > Is there already WIP for the data integrity issue fix? > OK. I see your patch set. > If there is anything I can do to assist, run the benchmark or anything > please let me know. > > In the meanwhile, I will run the benchmark with XFS_IOLOCK_SHARED > on the write() path. > As expected, results without exclusive iolock look very good [*]. Thanks, Amir. [*] I ran the following fio workload on e2-standard-8 GCE machine: [global] filename=/mnt/xfs/testfile.fio norandommap randrepeat=0 size=5G bs=8K ioengine=psync numjobs=8 group_reporting=1 direct=0 fallocate=1 end_fsync=0 runtime=60 [xfs-read] readwrite=randread [xfs-write] readwrite=randwrite ========================= v6.0-rc4 (BAD) ========= Run #1: READ: bw=7053KiB/s (7223kB/s) WRITE: bw=155MiB/s (163MB/s) Run #2: READ: bw=4672KiB/s (4784kB/s) WRITE: bw=355MiB/s (372MB/s) Run #3: READ: bw=5887KiB/s (6028kB/s) WRITE: bw=137MiB/s (144MB/s) ========================= v6.0-rc4 (read no iolock like ext4 - GOOD) ========= READ: bw=742MiB/s (778MB/s) WRITE: bw=345MiB/s (361MB/s) ========================= v6.0-rc4 (write shared iolock - BETTER) ========= Run #1: READ: bw=762MiB/s (799MB/s) WRITE: bw=926MiB/s (971MB/s) Run #2: READ: bw=170MiB/s (178MB/s) WRITE: bw=982MiB/s (1029MB/s) Run #3: READ: bw=755MiB/s (792MB/s) WRITE: bw=933MiB/s (978MB/s) ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-07 23:27 ` Dave Chinner 2019-04-08 9:02 ` Amir Goldstein @ 2019-04-08 11:03 ` Jan Kara 2019-04-22 10:55 ` Boaz Harrosh 1 sibling, 1 reply; 41+ messages in thread From: Jan Kara @ 2019-04-08 11:03 UTC (permalink / raw) To: Dave Chinner Cc: Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Mon 08-04-19 09:27:28, Dave Chinner wrote: > The result of this is that, AFAICT, ext4 does not protect against > read() vs hole punch races - it's hole punching code it does: > > Hole Punch: read(): > > inode_lock() > inode_dio_wait(inode); > down_write(i_mmap_sem) > truncate_pagecache_range() > ext4_file_iter_read() > ext4_map_blocks() > down_read(i_data_sem) > <gets mapping> > <populates page cache over hole> > <reads stale data into cache> > ..... > down_write(i_data_sem) > remove extents > > IOWs, ext4 is safe against truncate because of the > change-inode-size-before-invalidation hacks, but the lack of > serialise buffered reads means that hole punch and other similar > fallocate based extent manipulations can race against reads.... Hum, you are right. Ext4 is buggy in this regard. I've fixed the race for page fault in ea3d7209ca01 "ext4: fix races between page faults and hole punching" but didn't realize the problem is there for buffered reads as well. I'll think how we can fix this. Thanks for noticing this! Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 11:03 ` Jan Kara @ 2019-04-22 10:55 ` Boaz Harrosh 0 siblings, 0 replies; 41+ messages in thread From: Boaz Harrosh @ 2019-04-22 10:55 UTC (permalink / raw) To: Jan Kara, Dave Chinner Cc: Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On 08/04/19 14:03, Jan Kara wrote: <> > Hum, you are right. Ext4 is buggy in this regard. I've fixed the race for > page fault in ea3d7209ca01 "ext4: fix races between page faults and hole > punching" but didn't realize the problem is there for buffered reads as > well. I'll think how we can fix this. Thanks for noticing this! > This is very interesting. Please CC me if you have devised a test for this? For a long time I want to enhance fsstress --verify that each writer always writes the long address it writes to as data (ie. file looks like an increasing long counter) And readers want to see only this pattern or zero. > Honza > Thanks Boaz ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-04 21:17 ` Dave Chinner 2019-04-05 14:02 ` Amir Goldstein @ 2019-04-08 10:33 ` Jan Kara 2019-04-08 16:37 ` Davidlohr Bueso 1 sibling, 1 reply; 41+ messages in thread From: Jan Kara @ 2019-04-08 10:33 UTC (permalink / raw) To: Dave Chinner Cc: Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel, Davidlohr Bueso On Fri 05-04-19 08:17:30, Dave Chinner wrote: > FYI, I'm working on a range lock implementation that should both > solve the performance issue and the reader starvation issue at the > same time by allowing concurrent buffered reads and writes to > different file ranges. Are you aware of range locks Davidlohr has implemented [1]? It didn't get merged because he had no in-tree user at the time (he was more aiming at converting mmap_sem which is rather difficult). But the generic lock implementation should be well usable. Added Davidlohr to CC. Honza [1] https://lkml.org/lkml/2017/3/7/22 -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 10:33 ` Jan Kara @ 2019-04-08 16:37 ` Davidlohr Bueso 0 siblings, 0 replies; 41+ messages in thread From: Davidlohr Bueso @ 2019-04-08 16:37 UTC (permalink / raw) To: Jan Kara, Dave Chinner Cc: Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > FYI, I'm working on a range lock implementation that should both > > solve the performance issue and the reader starvation issue at the > > same time by allowing concurrent buffered reads and writes to > > different file ranges. > > Are you aware of range locks Davidlohr has implemented [1]? It didn't get > merged because he had no in-tree user at the time (he was more aiming at > converting mmap_sem which is rather difficult). But the generic lock > implementation should be well usable. > > Added Davidlohr to CC. > > Honza > > [1] https://lkml.org/lkml/2017/3/7/22 fyi this was the latest version (had some naming updates per peterz). https://lkml.org/lkml/2018/2/4/232 ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload @ 2019-04-08 16:37 ` Davidlohr Bueso 0 siblings, 0 replies; 41+ messages in thread From: Davidlohr Bueso @ 2019-04-08 16:37 UTC (permalink / raw) To: Jan Kara, Dave Chinner Cc: Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > FYI, I'm working on a range lock implementation that should both > > solve the performance issue and the reader starvation issue at the > > same time by allowing concurrent buffered reads and writes to > > different file ranges. > > Are you aware of range locks Davidlohr has implemented [1]? It didn't get > merged because he had no in-tree user at the time (he was more aiming at > converting mmap_sem which is rather difficult). But the generic lock > implementation should be well usable. > > Added Davidlohr to CC. > > Honza > > [1] https://lkml.org/lkml/2017/3/7/22 fyi this was the latest version (had some naming updates per peterz). https://lkml.org/lkml/2018/2/4/232 ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-08 16:37 ` Davidlohr Bueso (?) @ 2019-04-11 1:11 ` Dave Chinner 2019-04-16 12:22 ` Dave Chinner -1 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2019-04-11 1:11 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Mon, Apr 08, 2019 at 09:37:09AM -0700, Davidlohr Bueso wrote: > On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > > FYI, I'm working on a range lock implementation that should both > > > solve the performance issue and the reader starvation issue at the > > > same time by allowing concurrent buffered reads and writes to > > > different file ranges. > > > > Are you aware of range locks Davidlohr has implemented [1]? It didn't get > > merged because he had no in-tree user at the time (he was more aiming at > > converting mmap_sem which is rather difficult). But the generic lock > > implementation should be well usable. > > > > Added Davidlohr to CC. > > > > Honza > > > > [1] https://lkml.org/lkml/2017/3/7/22 > > fyi this was the latest version (had some naming updates per peterz). > > https://lkml.org/lkml/2018/2/4/232 No, I wasn't aware of these because they haven't ever been posted to a list I subscribe to and they haven't been merged. I'll go have a look at them over the next few days. Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-11 1:11 ` Dave Chinner @ 2019-04-16 12:22 ` Dave Chinner 2019-04-18 3:10 ` Dave Chinner 0 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2019-04-16 12:22 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Thu, Apr 11, 2019 at 11:11:17AM +1000, Dave Chinner wrote: > On Mon, Apr 08, 2019 at 09:37:09AM -0700, Davidlohr Bueso wrote: > > On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > > > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > > > FYI, I'm working on a range lock implementation that should both > > > > solve the performance issue and the reader starvation issue at the > > > > same time by allowing concurrent buffered reads and writes to > > > > different file ranges. > > > > > > Are you aware of range locks Davidlohr has implemented [1]? It didn't get > > > merged because he had no in-tree user at the time (he was more aiming at > > > converting mmap_sem which is rather difficult). But the generic lock > > > implementation should be well usable. > > > > > > Added Davidlohr to CC. > > > > > > Honza > > > > > > [1] https://lkml.org/lkml/2017/3/7/22 > > > > fyi this was the latest version (had some naming updates per peterz). > > > > https://lkml.org/lkml/2018/2/4/232 > > No, I wasn't aware of these because they haven't ever been posted to > a list I subscribe to and they haven't been merged. I'll go have a > look at them over the next few days. Rather disappointing, to tell the truth. The implementation doesn't scale nearly as a rwsem for concurrent IO using shared access (i.e. XFS direct IO). That's the baseline we need to get close to for range locks to be a viable prospect. Fio randrw numbers on a single file on a pmem device on a 16p machine using 4kB AIO-DIO iodepth 128 w/ fio on 5.1.0-rc3: IOPS read/write (direct IO) fio processes rwsem rangelock 1 78k / 78k 75k / 75k 2 131k / 131k 123k / 123k 4 267k / 267k 183k / 183k 8 372k / 372k 177k / 177k 16 315k / 315k 135k / 135k So uncontended, non-overlapping range performance is not really even in the ballpark right now, unfortunately. To indicate that range locking is actually working, let's do buffered read/write, which takes the rwsem exclusive for writes and so will be bound by that: IOPS read/write (buffered IO) fio processes rwsem rangelock 1 57k / 57k 64k / 64k 2 61k / 61k 111k / 111k 4 61k / 61k 228k / 228k 8 55k / 55k 195k / 195k 16 15k / 15k 40k / 40k So the win for mixed buffered IO is huge but it's at the cost of direct IO performance. We can't make that tradeoff, so if this implementation cannot be substantially improved we really can'ti use it. FUndamentally, the problem is that the interval tree work is all done under a spinlock, so by the time we get to 16p, 70% of the 16p that is being burnt is on the spinlock, and only 30% of the CPU time is actually doing IO work: + 70.78% 2.50% [kernel] [k] do_raw_spin_lock + 69.72% 0.07% [kernel] [k] _raw_spin_lock_irqsave - 68.27% 68.10% [kernel] [k] __pv_queued_spin_lock_slowpath ..... + 15.61% 0.07% [kernel] [k] range_write_unlock + 15.39% 0.06% [kernel] [k] range_read_unlock + 15.11% 0.12% [kernel] [k] range_read_lock + 15.11% 0.13% [kernel] [k] range_write_lock ..... + 12.92% 0.11% [kernel] [k] range_is_locked FWIW, I'm not convinced about the scalability of the rb/interval tree, to tell you the truth. We got rid of the rbtree in XFS for cache indexing because the multi-level pointer chasing was just too expensive to do under a spinlock - it's just not a cache efficient structure for random index object storage. FWIW, I have basic hack to replace the i_rwsem in XFS with a full range read or write lock with my XFS range lock implementation so it just behaves like a rwsem at this point. It is not in any way optimised at this point. Numbers for same AIO-DIO test are: IOPS read/write (direct IO) processes rwsem DB rangelock XFS rangelock 1 78k / 78k 75k / 75k 74k / 74k 2 131k / 131k 123k / 123k 134k / 134k 4 267k / 267k 183k / 183k 246k / 246k 8 372k / 372k 177k / 177k 306k / 306k 16 315k / 315k 135k / 135k 240k / 240k Performance is much closer to rwsems, but the single lock critical section still causes serious amounts of cacheline contention on pure shared-read lock workloads like this. FWIW, the XFS rangelock numbers match what I've been seeing with userspace perf tests using unoptimised pthread mutexes - ~600,000 lock/unlock cycles a second over ~100 concurrent non-overlapping ranges seem to be the limitation before futex contention burns down the house AS it is, I've done all the work to make XFS use proper range locks on top of your patch - I'll go back tomorrow and modify the XFS range locks to use the same API as your lock implementation. I'm interested to see what falls out when they are used as real range locks rather than a glorified rwsem.... Cheers, Dave. PS: there's a double lock bug in range_is_locked()..... -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-16 12:22 ` Dave Chinner @ 2019-04-18 3:10 ` Dave Chinner 2019-04-18 18:21 ` Davidlohr Bueso 0 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2019-04-18 3:10 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Tue, Apr 16, 2019 at 10:22:40PM +1000, Dave Chinner wrote: > On Thu, Apr 11, 2019 at 11:11:17AM +1000, Dave Chinner wrote: > > On Mon, Apr 08, 2019 at 09:37:09AM -0700, Davidlohr Bueso wrote: > > > On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > > > > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > > > > FYI, I'm working on a range lock implementation that should both > > > > > solve the performance issue and the reader starvation issue at the > > > > > same time by allowing concurrent buffered reads and writes to > > > > > different file ranges. > > > > > > > > Are you aware of range locks Davidlohr has implemented [1]? It didn't get > > > > merged because he had no in-tree user at the time (he was more aiming at > > > > converting mmap_sem which is rather difficult). But the generic lock > > > > implementation should be well usable. > > > > > > > > Added Davidlohr to CC. ..... > Fio randrw numbers on a single file on a pmem device on a 16p > machine using 4kB AIO-DIO iodepth 128 w/ fio on 5.1.0-rc3: > > IOPS read/write (direct IO) > fio processes rwsem rangelock > 1 78k / 78k 75k / 75k > 2 131k / 131k 123k / 123k > 4 267k / 267k 183k / 183k > 8 372k / 372k 177k / 177k > 16 315k / 315k 135k / 135k .... > FWIW, I'm not convinced about the scalability of the rb/interval > tree, to tell you the truth. We got rid of the rbtree in XFS for > cache indexing because the multi-level pointer chasing was just too > expensive to do under a spinlock - it's just not a cache efficient > structure for random index object storage. Yeah, definitely not convinced an rbtree is the right structure here. Locking of the tree is the limitation.... > FWIW, I have basic hack to replace the i_rwsem in XFS with a full > range read or write lock with my XFS range lock implementation so it > just behaves like a rwsem at this point. It is not in any way > optimised at this point. Numbers for same AIO-DIO test are: Now the stuff I've been working on has the same interface as Davidlohr's patch, so I can swap and change them without thinking about it. It's still completely unoptimised, but: IOPS read/write (direct IO) processes rwsem DB rangelock XFS rangelock 1 78k / 78k 75k / 75k 72k / 72k 2 131k / 131k 123k / 123k 133k / 133k 4 267k / 267k 183k / 183k 237k / 237k 8 372k / 372k 177k / 177k 265k / 265k 16 315k / 315k 135k / 135k 228k / 228k It's still substantially faster than the interval tree code. BTW, if I take away the rwsem serialisation altogether, this test tops out at just under 500k/500k at 8 threads, and at 16 threads has started dropping off (~440k/440k). So the rwsem is a scalability limitation at just 8 threads.... /me goes off and thinks more about adding optimistic lock coupling to the XFS iext btree to get rid of the need for tree-wide locking altogether Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-18 3:10 ` Dave Chinner @ 2019-04-18 18:21 ` Davidlohr Bueso 0 siblings, 0 replies; 41+ messages in thread From: Davidlohr Bueso @ 2019-04-18 18:21 UTC (permalink / raw) To: Dave Chinner Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Thu, 2019-04-18 at 13:10 +1000, Dave Chinner wrote: > Now the stuff I've been working on has the same interface as > Davidlohr's patch, so I can swap and change them without thinking > about it. It's still completely unoptimised, but: > > IOPS read/write (direct IO) > processes rwsem DB rangelock XFS > rangelock > 1 78k / 78k 75k / 75k 72k / 72k > 2 131k / 131k 123k / 123k 133k / 133k > 4 267k / 267k 183k / 183k 237k / 237k > 8 372k / 372k 177k / 177k 265k / 265k > 16 315k / 315k 135k / 135k 228k / 228k > > It's still substantially faster than the interval tree code. In general another big difference between both rangelock vs rwsems (when comparing them with full ranges) is that the latter will do writer optimistic spinning, so saving a context switch under the right scenarios provides mayor wins for rwsems -- I'm not sure if this applies to your fio tests, though. And pretty soon readers will also do this, hence rwsem will become a try-hard-not-to-sleep lock. One of the reasons why I was hesitant with Btrees was the fact that insertion requires memory allocation, something I wanted to avoid... per your numbers, sacrificing tree depth was the wrong choice. Thanks for sharing these numbers. > > BTW, if I take away the rwsem serialisation altogether, this > test tops out at just under 500k/500k at 8 threads, and at 16 > threads has started dropping off (~440k/440k). So the rwsem is > a scalability limitation at just 8 threads.... > > /me goes off and thinks more about adding optimistic lock coupling > to the XFS iext btree to get rid of the need for tree-wide > locking altogether I was not aware of this code. Thanks, Davidlohr ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload @ 2019-04-18 18:21 ` Davidlohr Bueso 0 siblings, 0 replies; 41+ messages in thread From: Davidlohr Bueso @ 2019-04-18 18:21 UTC (permalink / raw) To: Dave Chinner Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Thu, 2019-04-18 at 13:10 +1000, Dave Chinner wrote: > Now the stuff I've been working on has the same interface as > Davidlohr's patch, so I can swap and change them without thinking > about it. It's still completely unoptimised, but: > > IOPS read/write (direct IO) > processes rwsem DB rangelock XFS > rangelock > 1 78k / 78k 75k / 75k 72k / 72k > 2 131k / 131k 123k / 123k 133k / 133k > 4 267k / 267k 183k / 183k 237k / 237k > 8 372k / 372k 177k / 177k 265k / 265k > 16 315k / 315k 135k / 135k 228k / 228k > > It's still substantially faster than the interval tree code. In general another big difference between both rangelock vs rwsems (when comparing them with full ranges) is that the latter will do writer optimistic spinning, so saving a context switch under the right scenarios provides mayor wins for rwsems -- I'm not sure if this applies to your fio tests, though. And pretty soon readers will also do this, hence rwsem will become a try-hard-not-to-sleep lock. One of the reasons why I was hesitant with Btrees was the fact that insertion requires memory allocation, something I wanted to avoid... per your numbers, sacrificing tree depth was the wrong choice. Thanks for sharing these numbers. > > BTW, if I take away the rwsem serialisation altogether, this > test tops out at just under 500k/500k at 8 threads, and at 16 > threads has started dropping off (~440k/440k). So the rwsem is > a scalability limitation at just 8 threads.... > > /me goes off and thinks more about adding optimistic lock coupling > to the XFS iext btree to get rid of the need for tree-wide > locking altogether I was not aware of this code. Thanks, Davidlohr ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-18 18:21 ` Davidlohr Bueso (?) @ 2019-04-20 23:54 ` Dave Chinner 2019-05-03 4:17 ` Dave Chinner -1 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2019-04-20 23:54 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Thu, Apr 18, 2019 at 11:21:34AM -0700, Davidlohr Bueso wrote: > On Thu, 2019-04-18 at 13:10 +1000, Dave Chinner wrote: > > Now the stuff I've been working on has the same interface as > > Davidlohr's patch, so I can swap and change them without thinking > > about it. It's still completely unoptimised, but: > > > > IOPS read/write (direct IO) > > processes rwsem DB rangelock XFS > > rangelock > > 1 78k / 78k 75k / 75k 72k / 72k > > 2 131k / 131k 123k / 123k 133k / 133k > > 4 267k / 267k 183k / 183k 237k / 237k > > 8 372k / 372k 177k / 177k 265k / 265k > > 16 315k / 315k 135k / 135k 228k / 228k > > > > It's still substantially faster than the interval tree code. > > In general another big difference between both rangelock vs rwsems > (when comparing them with full ranges) is that the latter will do > writer optimistic spinning, so saving a context switch under the right > scenarios provides mayor wins for rwsems -- I'm not sure if this > applies to your fio tests, though. And pretty soon readers will also do > this, hence rwsem will become a try-hard-not-to-sleep lock. Right, the optimistic spin-on-owner behaviour basically causes both rwsems and mutexes to behave as spin locks under these fio workloads until all CPUs are spinning at 100% CPU usage before they even start to behave like a sleeping lock. Essentailly, when I'm using the XFS range locks as "full range only" rwsem equivalent locks, they end up behaving like rwsems in terms of spinning on the tree mutex as the single read-lock range is shared between all concurrent readers and so has relatively low lookup and modification cost. If I optmised the record update, it would be even closer to the rwsem performance, but full range read locks are going to be rare. Hell, even conflicting lock ranges are going to be rare in the IO path, because the application is doing something very wrong if it is doing overlapping concurrent IOs.... > One of the reasons why I was hesitant with Btrees was the fact that > insertion requires memory allocation, something I wanted to avoid... Yup, that's an issue, and one of the reasons why I've used a mutex for the tree lock rather than a spin lock. But in the end, there's no difference to CPU usage on contention as they both act as spin locks in these cases... If it becomes an issue, I'll add a mempool for the tree nodes and make sure that it is pre-populated sufficiently before starting a multi-level tree modification. > per your numbers, sacrificing tree depth was the wrong choice. Thanks > for sharing these numbers. Yeah, anything that pointer chases through cachelines and dirties multiple cachelines on rebalance really doesn't scale for a fast-lookup structure. For btrees multi-level split/merge hurt, but for the lookup and simple insert/remove case the cacheline miss cost is substantially amortised by packing multiple records per cacheline. > > BTW, if I take away the rwsem serialisation altogether, this > > test tops out at just under 500k/500k at 8 threads, and at 16 > > threads has started dropping off (~440k/440k). So the rwsem is > > a scalability limitation at just 8 threads.... > > > > /me goes off and thinks more about adding optimistic lock coupling > > to the XFS iext btree to get rid of the need for tree-wide > > locking altogether > > I was not aware of this code. It's relatively new, and directly tailored to the needs of caching the XFS extent tree - it's not really a generic btree in that it's record store format is the XFS on-disk extent record. i.e. it only stores 54 bits of start offset and 21 bits of length in it's 16 byte records, and the rest of the space is for the record data. As such, I'm not really implementing a generic range lock - it is highly tailored to the requirements and constraints of XFS filesystem IO. e.g. using max(block size, PAGE_SIZE) granularity range indexing means we can support maximum IO sizes (4GB) with 21 bits of length in the record. And RANGE_LOCK_FULL is implemented as length = MAXEXTLEN + a hidden state bit so it supports exclusive locking from (start, RANGE_LOCK_FULL) and things like truncate, EOF zeroing use this to exclude IO from the range they are working on correctly.... Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-04-20 23:54 ` Dave Chinner @ 2019-05-03 4:17 ` Dave Chinner 2019-05-03 5:17 ` Dave Chinner 0 siblings, 1 reply; 41+ messages in thread From: Dave Chinner @ 2019-05-03 4:17 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Sun, Apr 21, 2019 at 09:54:12AM +1000, Dave Chinner wrote: > On Thu, Apr 18, 2019 at 11:21:34AM -0700, Davidlohr Bueso wrote: > > On Thu, 2019-04-18 at 13:10 +1000, Dave Chinner wrote: > > > Now the stuff I've been working on has the same interface as > > > Davidlohr's patch, so I can swap and change them without thinking > > > about it. It's still completely unoptimised, but: > > > > > > IOPS read/write (direct IO) > > > processes rwsem DB rangelock XFS > > > rangelock > > > 1 78k / 78k 75k / 75k 72k / 72k > > > 2 131k / 131k 123k / 123k 133k / 133k > > > 4 267k / 267k 183k / 183k 237k / 237k > > > 8 372k / 372k 177k / 177k 265k / 265k > > > 16 315k / 315k 135k / 135k 228k / 228k > > > > > > It's still substantially faster than the interval tree code. .... > > > /me goes off and thinks more about adding optimistic lock coupling > > > to the XFS iext btree to get rid of the need for tree-wide > > > locking altogether > > > > I was not aware of this code. > > It's relatively new, and directly tailored to the needs of caching > the XFS extent tree - it's not really a generic btree in that it's > record store format is the XFS on-disk extent record. i.e. it > only stores 54 bits of start offset and 21 bits of length in it's 16 > byte records, and the rest of the space is for the record data. SO now I have a mostly working OLC btree based on this tree which is plumbed into xfsprogs userspace and some testing code. I think I can say now that the code will actually work, and it /should/ scale better than a rwsem. The userspace test harness that I have ran a "thread profile" to indicated scalability. Basically it ran each thread in a different offset range and locked a hundred ranges and then unlocked them, and then looped over this. The btree is a single level for the first 14 locks, 2-level for up to 210 locks, and 3-level for up to 3150 locks. Hence most of this testing results in the btree being 2-3 levels and so largely removes the global root node lock as a point of contention. It's "best case" for concurrency for an OLC btree. On a 16p machine: Range lock/unlock ops/s threads mutex btree OLC btree 1 5239442 949487 2 1014466 1398539 4 985940 2405275 8 733195 3288435 16 653429 2809225 When looking at these numbers, remember that the mutex btree kernel range lock performed a lot better than the interval tree range lock, and they were only ~30% down on an rwsem. The mutex btree code shows cache residency effects for the single threaded load, hence it looks much faster than it is for occasional and multithreaded access. However, at 2 threads (where hot CPU caches don't affect the performance), the OLC btree is 40% faster, and at 8 threads it is 4.5x faster than the mutex btree. The OLC btree starts slowing down at 16 threads, largely because the tree itself doesn't have enough depth to provide the interior nodes to scale to higher concurrency levels without contention, but it's still running at 4.5x faster than the mutex btree.... The best part is when I run worse case threaded workloads on the OLC btree. If I run the same 100-lock loops, but this time change the offsets of each thread so they interleave into adjacent records in the btree (i.e. every thread touches every leaf), then the performance is still pretty damn good: Range lock/unlock ops/s threads Worst Case Best Case 1 1045991 949487 2 1530212 1398539 4 1147099 2405275 8 1602114 3288435 16 1731890 2809225 IOWs, performance is down and somewhat variable around tree height changes (4 threads straddles the 2-3 level tree height threshold), but it's still a massive improvement on the mutex_btree and it's not going backwards as threads are added. Concept proven. Next steps are: - separate the OLC btree from the XFS iext btree implementation. It will still have a similar interface (i.e. can't manipulate the btree records directly), but there's sufficient difference in structure for them to be separate implementations. - expand records out to full 64bit extents. The iext tree memory usage constraints no longer apply, so the record size can go up a little bit. - work out whether RCU read locking and kfree_rcu() will work with the requirement to do memory allocation while holding rcu_read_lock(). Alternative is an internal garbage collector mechanism, kinda like I've hacked up to simulate kfree_rcu() in userspace. - fix all the little bugs that still exist in the code. - Think about structural optimisations like parent pointers to avoid costly path walks to find parents for modifications. Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload 2019-05-03 4:17 ` Dave Chinner @ 2019-05-03 5:17 ` Dave Chinner 0 siblings, 0 replies; 41+ messages in thread From: Dave Chinner @ 2019-05-03 5:17 UTC (permalink / raw) To: Davidlohr Bueso Cc: Jan Kara, Amir Goldstein, Darrick J . Wong, Christoph Hellwig, Matthew Wilcox, linux-xfs, linux-fsdevel On Fri, May 03, 2019 at 02:17:27PM +1000, Dave Chinner wrote: > Concept proven. > > Next steps are: .... > - work out whether RCU read locking and kfree_rcu() will > work with the requirement to do memory allocation while > holding rcu_read_lock(). Alternative is an internal > garbage collector mechanism, kinda like I've hacked up to > simulate kfree_rcu() in userspace. Internal RCU interactions are now solved. Actually very simple in the end, should be very easy to integrate into the code. Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 41+ messages in thread
* [xfs] fa3fe73bed: aim7.jobs-per-min -10.9% regression 2019-04-04 16:57 [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload Amir Goldstein 2019-04-04 21:17 ` Dave Chinner @ 2019-04-08 9:14 ` kernel test robot 1 sibling, 0 replies; 41+ messages in thread From: kernel test robot @ 2019-04-08 9:14 UTC (permalink / raw) To: lkp [-- Attachment #1: Type: text/plain, Size: 116383 bytes --] Greeting, FYI, we noticed a -10.9% regression of aim7.jobs-per-min due to commit: commit: fa3fe73bed17967cb623461b166c46dcffb661a7 ("[POC][PATCH] xfs: reduce ilock contention on buffered randrw workload") url: https://github.com/0day-ci/linux/commits/Amir-Goldstein/xfs-reduce-ilock-contention-on-buffered-randrw-workload/20190405-100748 in testcase: aim7 on test machine: 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory with following parameters: disk: 4BRD_12G md: RAID0 fs: xfs test: disk_rr load: 3000 cpufreq_governor: performance test-description: AIM7 is a traditional UNIX system level benchmark suite which is used to test and measure the performance of multiuser system. test-url: https://sourceforge.net/projects/aimbench/files/aim-suite7/ In addition to that, the commit also has significant impact on the following tests: +------------------+-----------------------------------------------------------------------+ | testcase: change | vm-scalability: vm-scalability.median -5.2% regression | | test machine | 4 threads Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz with 8G memory | | test parameters | cpufreq_governor=performance | | | runtime=300s | | | test=lru-file-readonce | | | ucode=0x20 | +------------------+-----------------------------------------------------------------------+ | testcase: change | aim7: aim7.jobs-per-min -79.4% regression | | test machine | 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory | | test parameters | cpufreq_governor=performance | | | disk=4BRD_12G | | | fs=xfs | | | load=3000 | | | md=RAID1 | | | test=disk_cp | +------------------+-----------------------------------------------------------------------+ Details are as below: --------------------------------------------------------------------------------------------------> To reproduce: git clone https://github.com/intel/lkp-tests.git cd lkp-tests bin/lkp install job.yaml # job file is attached in this email bin/lkp run job.yaml ========================================================================================= compiler/cpufreq_governor/disk/fs/kconfig/load/md/rootfs/tbox_group/test/testcase: gcc-7/performance/4BRD_12G/xfs/x86_64-rhel-7.6/3000/RAID0/debian-x86_64-2018-04-03.cgz/lkp-ivb-ep01/disk_rr/aim7 commit: 8e22ba96d4 (" RISC-V Patches for 5.1-rc4") fa3fe73bed ("xfs: reduce ilock contention on buffered randrw workload") 8e22ba96d44c4ad5 fa3fe73bed17967cb623461b166 ---------------- --------------------------- %stddev %change %stddev \ | \ 174264 -10.9% 155325 aim7.jobs-per-min 103.67 +12.2% 116.34 aim7.time.elapsed_time 103.67 +12.2% 116.34 aim7.time.elapsed_time.max 13290 ± 7% +1050.1% 152859 aim7.time.involuntary_context_switches 2760 ± 2% +5.7% 2917 aim7.time.maximum_resident_set_size 148794 ± 2% +11.8% 166280 aim7.time.minor_page_faults 2305 +68.6% 3887 aim7.time.system_time 313.88 -56.9% 135.37 aim7.time.user_time 1087532 -48.9% 555946 aim7.time.voluntary_context_switches 38.60 ± 2% -59.6% 15.61 iostat.cpu.idle 53.90 +51.0% 81.41 iostat.cpu.system 7.49 -60.2% 2.98 iostat.cpu.user 37.49 ± 2% -23.3 14.14 mpstat.cpu.all.idle% 0.00 ± 39% -0.0 0.00 ± 55% mpstat.cpu.all.iowait% 0.03 ± 63% -0.0 0.00 ±130% mpstat.cpu.all.soft% 54.86 +28.0 82.83 mpstat.cpu.all.sys% 7.62 -4.6 3.02 mpstat.cpu.all.usr% 38.00 -60.5% 15.00 vmstat.cpu.id 53.00 +52.8% 81.00 vmstat.cpu.sy 23.75 +53.0% 36.33 vmstat.procs.r 21582 -51.9% 10376 vmstat.system.cs 80340 +2.6% 82446 vmstat.system.in 6656 ± 4% +301.7% 26743 meminfo.Active(file) 1398433 -16.5% 1167608 meminfo.Dirty 1416644 -17.3% 1171397 meminfo.Inactive 1397201 -17.6% 1151246 meminfo.Inactive(file) 29353 ± 2% +42.4% 41789 ± 3% meminfo.Shmem 41450 ± 2% -14.2% 35584 meminfo.max_used_kB 70509709 ± 41% -70.9% 20493630 ± 3% cpuidle.C1.time 689042 ± 44% -70.2% 205612 ± 4% cpuidle.C1.usage 69060244 ± 48% -39.8% 41576976 ± 35% cpuidle.C1E.time 554731 ± 58% -56.4% 241775 ± 33% cpuidle.C1E.usage 1.13e+09 ± 12% -58.3% 4.715e+08 ± 3% cpuidle.C6.time 2020589 ± 9% -65.1% 705482 ± 2% cpuidle.C6.usage 44479 ± 3% -73.1% 11947 ± 3% cpuidle.POLL.time 3370 ± 2% +292.1% 13213 numa-meminfo.node0.Active(file) 695340 -16.3% 581687 numa-meminfo.node0.Dirty 1359044 -10.6% 1215608 numa-meminfo.node0.FilePages 707196 -17.1% 586045 numa-meminfo.node0.Inactive 694427 -17.4% 573469 numa-meminfo.node0.Inactive(file) 3130 ± 4% +334.3% 13594 numa-meminfo.node1.Active(file) 699736 -16.2% 586092 numa-meminfo.node1.Dirty 706171 -17.1% 585519 ± 2% numa-meminfo.node1.Inactive 699495 -17.4% 577906 numa-meminfo.node1.Inactive(file) 2905 ± 10% +19.3% 3465 ± 7% slabinfo.Acpi-Namespace.active_objs 2905 ± 10% +19.3% 3465 ± 7% slabinfo.Acpi-Namespace.num_objs 1005 ± 8% +26.6% 1272 ± 4% slabinfo.blkdev_ioc.active_objs 1005 ± 8% +26.6% 1272 ± 4% slabinfo.blkdev_ioc.num_objs 2764 -12.7% 2413 slabinfo.dmaengine-unmap-16.active_objs 2834 -14.8% 2413 slabinfo.dmaengine-unmap-16.num_objs 2308 ± 6% +17.9% 2722 ± 4% slabinfo.kmalloc-128.active_objs 2308 ± 6% +17.9% 2722 ± 4% slabinfo.kmalloc-128.num_objs 2366 -10.8% 2109 slabinfo.xfs_inode.active_objs 2436 -11.1% 2164 slabinfo.xfs_inode.num_objs 861.75 ± 2% +284.9% 3317 ± 2% numa-vmstat.node0.nr_active_file 174078 -16.8% 144873 numa-vmstat.node0.nr_dirty 340009 -10.8% 303329 numa-vmstat.node0.nr_file_pages 173830 -17.9% 142779 numa-vmstat.node0.nr_inactive_file 862.00 ± 2% +284.5% 3314 ± 2% numa-vmstat.node0.nr_zone_active_file 173830 -17.9% 142774 numa-vmstat.node0.nr_zone_inactive_file 174355 -16.8% 145128 numa-vmstat.node0.nr_zone_write_pending 793.00 ± 3% +322.9% 3353 numa-vmstat.node1.nr_active_file 175039 -16.7% 145725 numa-vmstat.node1.nr_dirty 174980 -17.9% 143680 numa-vmstat.node1.nr_inactive_file 795.00 ± 3% +321.3% 3349 numa-vmstat.node1.nr_zone_active_file 174981 -17.9% 143677 numa-vmstat.node1.nr_zone_inactive_file 175254 -16.7% 145951 numa-vmstat.node1.nr_zone_write_pending 89307 +3.9% 92750 proc-vmstat.nr_active_anon 1631 ± 3% +310.5% 6697 proc-vmstat.nr_active_file 349106 -16.4% 291910 proc-vmstat.nr_dirty 671274 -8.0% 617399 proc-vmstat.nr_file_pages 4860 +3.8% 5044 proc-vmstat.nr_inactive_anon 348815 -17.5% 287737 proc-vmstat.nr_inactive_file 5958 +2.7% 6117 proc-vmstat.nr_mapped 7337 ± 2% +42.4% 10450 ± 3% proc-vmstat.nr_shmem 89307 +3.9% 92750 proc-vmstat.nr_zone_active_anon 1631 ± 3% +310.5% 6697 proc-vmstat.nr_zone_active_file 4860 +3.8% 5044 proc-vmstat.nr_zone_inactive_anon 348814 -17.5% 287736 proc-vmstat.nr_zone_inactive_file 349664 -16.4% 292363 proc-vmstat.nr_zone_write_pending 561.75 ±129% +2428.7% 14205 proc-vmstat.numa_hint_faults 2127 ± 18% +534.8% 13501 ± 5% proc-vmstat.numa_pages_migrated 69610469 +9.7% 76384348 proc-vmstat.pgactivate 444949 +10.3% 490981 proc-vmstat.pgfault 2127 ± 18% +534.8% 13501 ± 5% proc-vmstat.pgmigrate_success 767.75 +234.0% 2564 turbostat.Avg_MHz 63.61 +22.6 86.26 turbostat.Busy% 1206 +146.4% 2973 turbostat.Bzy_MHz 685178 ± 44% -70.7% 200607 ± 4% turbostat.C1 1.64 ± 39% -1.2 0.43 ± 2% turbostat.C1% 554320 ± 58% -56.5% 241296 ± 33% turbostat.C1E 1.61 ± 48% -0.7 0.88 ± 35% turbostat.C1E% 2016855 ± 9% -65.2% 702260 ± 2% turbostat.C6 26.40 ± 11% -16.4 9.97 ± 2% turbostat.C6% 27.23 ± 2% -68.8% 8.49 ± 7% turbostat.CPU%c1 1.55 ± 70% -86.5% 0.21 ± 57% turbostat.CPU%c3 46.47 +210.0% 144.08 turbostat.CorWatt 59.50 +19.3% 71.00 turbostat.CoreTmp 8684289 +13.4% 9851854 turbostat.IRQ 4.56 ± 19% -47.5% 2.39 ± 9% turbostat.Pkg%pc2 59.50 +19.3% 71.00 turbostat.PkgTmp 72.91 +134.8% 171.23 turbostat.PkgWatt 33.43 +1.5% 33.94 turbostat.RAMWatt 8530 +10.7% 9440 turbostat.SMI 6.38 ± 11% -32.0% 4.33 ± 39% sched_debug.cfs_rq:/.load_avg.min 514985 +66.0% 855038 sched_debug.cfs_rq:/.min_vruntime.avg 597546 ± 2% +60.1% 956564 ± 2% sched_debug.cfs_rq:/.min_vruntime.max 496727 +66.9% 829055 sched_debug.cfs_rq:/.min_vruntime.min 0.51 ± 3% +19.5% 0.61 ± 4% sched_debug.cfs_rq:/.nr_running.avg 0.43 ± 5% -31.3% 0.29 ± 5% sched_debug.cfs_rq:/.nr_running.stddev 2.86 ±115% +296.8% 11.36 ± 66% sched_debug.cfs_rq:/.removed.util_avg.avg 75.12 ±100% +160.7% 195.83 ± 20% sched_debug.cfs_rq:/.removed.util_avg.max 14.08 ±105% +184.6% 40.08 ± 36% sched_debug.cfs_rq:/.removed.util_avg.stddev 11.50 +20.3% 13.83 ± 2% sched_debug.cfs_rq:/.runnable_load_avg.avg 31.50 ± 6% +33.9% 42.17 ± 20% sched_debug.cfs_rq:/.runnable_load_avg.max 11118 ± 4% -35.2% 7203 ± 15% sched_debug.cfs_rq:/.runnable_weight.stddev 675.05 +15.4% 778.94 ± 5% sched_debug.cfs_rq:/.util_avg.avg 1251 ± 6% +38.8% 1737 ± 10% sched_debug.cfs_rq:/.util_avg.max 317.25 ± 16% -40.2% 189.67 ± 53% sched_debug.cfs_rq:/.util_avg.min 205.16 ± 8% +68.5% 345.67 ± 8% sched_debug.cfs_rq:/.util_avg.stddev 112.36 ± 6% +80.7% 203.05 ± 6% sched_debug.cfs_rq:/.util_est_enqueued.avg 573.00 ± 18% +45.3% 832.83 ± 23% sched_debug.cfs_rq:/.util_est_enqueued.max 524579 ± 6% -13.6% 453404 ± 3% sched_debug.cpu.avg_idle.avg 244291 ± 4% -9.1% 222083 ± 5% sched_debug.cpu.avg_idle.stddev 11.71 ± 4% -49.3% 5.94 ± 8% sched_debug.cpu.clock.stddev 11.71 ± 4% -49.3% 5.94 ± 8% sched_debug.cpu.clock_task.stddev 11.06 ± 6% +28.9% 14.26 ± 2% sched_debug.cpu.cpu_load[0].avg 29.25 ± 11% +56.1% 45.67 ± 24% sched_debug.cpu.cpu_load[0].max 12.07 ± 8% +27.6% 15.40 sched_debug.cpu.cpu_load[1].avg 13.73 ± 13% +22.1% 16.77 ± 2% sched_debug.cpu.cpu_load[2].avg 1.50 ± 84% +188.9% 4.33 ± 39% sched_debug.cpu.cpu_load[3].min 1142 ± 12% -25.3% 853.96 ± 4% sched_debug.cpu.curr->pid.stddev 14069 ± 7% -15.2% 11926 ± 12% sched_debug.cpu.load.stddev 0.00 ± 4% -16.6% 0.00 ± 3% sched_debug.cpu.next_balance.stddev 0.51 ± 4% +26.0% 0.64 ± 7% sched_debug.cpu.nr_running.avg 16934 -47.6% 8876 sched_debug.cpu.nr_switches.avg 25332 ± 2% -27.0% 18503 ± 6% sched_debug.cpu.nr_switches.max 14912 -52.7% 7050 sched_debug.cpu.nr_switches.min 66.50 ± 4% +95.7% 130.17 ± 15% sched_debug.cpu.nr_uninterruptible.max 9.88 ± 47% -682.3% -57.50 sched_debug.cpu.nr_uninterruptible.min 13.40 ± 8% +185.5% 38.27 ± 5% sched_debug.cpu.nr_uninterruptible.stddev 4.77 -100.0% 0.00 sched_debug.rt_rq:/.rt_runtime.stddev 13.52 ± 12% -60.7% 5.31 ± 11% perf-stat.i.MPKI 3.995e+09 +462.1% 2.245e+10 perf-stat.i.branch-instructions 2.58 ± 9% -1.5 1.09 ± 3% perf-stat.i.branch-miss-rate% 61148500 -10.7% 54581970 ± 2% perf-stat.i.branch-misses 15.27 ± 3% +5.0 20.26 perf-stat.i.cache-miss-rate% 24227403 ± 2% +35.1% 32730873 perf-stat.i.cache-misses 22100 -52.5% 10507 perf-stat.i.context-switches 2.05 ± 6% -32.9% 1.38 ± 3% perf-stat.i.cpi 3.059e+10 +235.1% 1.025e+11 perf-stat.i.cpu-cycles 1453 ± 2% +49.5% 2172 perf-stat.i.cpu-migrations 1212 ± 2% +142.2% 2937 perf-stat.i.cycles-between-cache-misses 2.10 ± 6% -1.2 0.85 ± 6% perf-stat.i.dTLB-load-miss-rate% 1.442e+08 ± 6% +73.1% 2.496e+08 ± 7% perf-stat.i.dTLB-load-misses 6.303e+09 +365.6% 2.935e+10 perf-stat.i.dTLB-loads 0.08 ± 9% -0.0 0.04 ± 12% perf-stat.i.dTLB-store-miss-rate% 3068070 ± 7% +24.7% 3826133 ± 15% perf-stat.i.dTLB-store-misses 4.064e+09 +309.2% 1.663e+10 perf-stat.i.dTLB-stores 8435967 ± 3% -25.8% 6259422 perf-stat.i.iTLB-load-misses 2.021e+10 +428.7% 1.069e+11 perf-stat.i.instructions 2390 ± 5% +560.1% 15782 perf-stat.i.instructions-per-iTLB-miss 0.62 +56.0% 0.97 perf-stat.i.ipc 20.68 +2.3 22.94 perf-stat.i.node-load-miss-rate% 2760936 +29.0% 3562738 perf-stat.i.node-load-misses 12616257 +6.2% 13392887 perf-stat.i.node-loads 19.20 ± 4% -3.2 16.04 perf-stat.i.node-store-miss-rate% 2286706 +31.6% 3009786 perf-stat.i.node-store-misses 10050267 ± 2% +70.0% 17083826 perf-stat.i.node-stores 8.39 -81.4% 1.56 perf-stat.overall.MPKI 1.53 -1.3 0.24 ± 2% perf-stat.overall.branch-miss-rate% 14.28 +5.3 19.58 perf-stat.overall.cache-miss-rate% 1.51 -36.6% 0.96 perf-stat.overall.cpi 1262 +147.9% 3131 perf-stat.overall.cycles-between-cache-misses 2.24 ± 6% -1.4 0.84 ± 7% perf-stat.overall.dTLB-load-miss-rate% 0.08 ± 6% -0.1 0.02 ± 15% perf-stat.overall.dTLB-store-miss-rate% 2398 ± 3% +612.0% 17076 perf-stat.overall.instructions-per-iTLB-miss 0.66 +57.8% 1.04 perf-stat.overall.ipc 17.95 +3.1 21.01 perf-stat.overall.node-load-miss-rate% 18.54 ± 2% -3.6 14.98 perf-stat.overall.node-store-miss-rate% 3.957e+09 +462.5% 2.226e+10 perf-stat.ps.branch-instructions 60563941 -10.7% 54108124 ± 2% perf-stat.ps.branch-misses 23995092 ± 2% +35.2% 32443881 perf-stat.ps.cache-misses 21887 -52.4% 10415 perf-stat.ps.context-switches 3.029e+10 +235.4% 1.016e+11 perf-stat.ps.cpu-cycles 1439 ± 2% +49.6% 2153 perf-stat.ps.cpu-migrations 1.428e+08 ± 6% +73.3% 2.474e+08 ± 7% perf-stat.ps.dTLB-load-misses 6.242e+09 +366.0% 2.909e+10 perf-stat.ps.dTLB-loads 3038630 ± 7% +24.8% 3792456 ± 15% perf-stat.ps.dTLB-store-misses 4.025e+09 +309.6% 1.649e+10 perf-stat.ps.dTLB-stores 8354826 ± 3% -25.7% 6204340 perf-stat.ps.iTLB-load-misses 2.002e+10 +429.1% 1.059e+11 perf-stat.ps.instructions 2734433 +29.1% 3531311 perf-stat.ps.node-load-misses 12494983 +6.2% 13274613 perf-stat.ps.node-loads 2264742 +31.7% 2983304 perf-stat.ps.node-store-misses 9953749 ± 2% +70.1% 16933523 perf-stat.ps.node-stores 2.12e+12 +484.3% 1.238e+13 perf-stat.total.instructions 212836 +10.4% 234958 interrupts.CPU0.LOC:Local_timer_interrupts 1104 ± 26% +260.6% 3984 ± 5% interrupts.CPU0.RES:Rescheduling_interrupts 212437 +10.6% 234923 interrupts.CPU1.LOC:Local_timer_interrupts 1004 ± 34% +237.6% 3392 ± 4% interrupts.CPU1.RES:Rescheduling_interrupts 212437 +10.5% 234681 interrupts.CPU10.LOC:Local_timer_interrupts 1254 ± 51% +158.9% 3246 interrupts.CPU10.RES:Rescheduling_interrupts 212545 +10.4% 234638 interrupts.CPU11.LOC:Local_timer_interrupts 721.50 ± 10% +454.4% 4000 ± 25% interrupts.CPU11.RES:Rescheduling_interrupts 212604 +10.4% 234633 interrupts.CPU12.LOC:Local_timer_interrupts 786.00 ± 6% +308.9% 3213 ± 2% interrupts.CPU12.RES:Rescheduling_interrupts 725.75 ± 12% +360.3% 3340 ± 2% interrupts.CPU13.RES:Rescheduling_interrupts 773.25 ± 93% +775.2% 6767 ± 28% interrupts.CPU14.NMI:Non-maskable_interrupts 773.25 ± 93% +775.2% 6767 ± 28% interrupts.CPU14.PMI:Performance_monitoring_interrupts 716.75 ± 10% +355.1% 3262 ± 3% interrupts.CPU14.RES:Rescheduling_interrupts 725.00 ± 8% +361.4% 3345 ± 5% interrupts.CPU15.RES:Rescheduling_interrupts 212119 +10.6% 234586 interrupts.CPU16.LOC:Local_timer_interrupts 390.25 ±172% +1285.7% 5407 ± 35% interrupts.CPU16.NMI:Non-maskable_interrupts 390.25 ±172% +1285.7% 5407 ± 35% interrupts.CPU16.PMI:Performance_monitoring_interrupts 692.25 ± 13% +428.8% 3660 ± 14% interrupts.CPU16.RES:Rescheduling_interrupts 212372 +10.5% 234579 interrupts.CPU17.LOC:Local_timer_interrupts 723.00 ± 10% +357.1% 3304 interrupts.CPU17.RES:Rescheduling_interrupts 212228 +10.6% 234681 interrupts.CPU18.LOC:Local_timer_interrupts 790.00 ± 10% +306.5% 3211 ± 3% interrupts.CPU18.RES:Rescheduling_interrupts 795.75 ± 14% +353.3% 3607 ± 3% interrupts.CPU19.RES:Rescheduling_interrupts 212317 +10.2% 233944 interrupts.CPU2.LOC:Local_timer_interrupts 956.00 ± 19% +377.3% 4562 ± 26% interrupts.CPU2.RES:Rescheduling_interrupts 212471 +10.5% 234677 interrupts.CPU20.LOC:Local_timer_interrupts 739.50 ± 11% +341.3% 3263 interrupts.CPU20.RES:Rescheduling_interrupts 751.75 ±170% +802.2% 6782 ± 28% interrupts.CPU21.NMI:Non-maskable_interrupts 751.75 ±170% +802.2% 6782 ± 28% interrupts.CPU21.PMI:Performance_monitoring_interrupts 666.75 ± 8% +401.0% 3340 interrupts.CPU21.RES:Rescheduling_interrupts 742.50 ± 14% +339.0% 3259 ± 2% interrupts.CPU22.RES:Rescheduling_interrupts 212505 +10.4% 234501 interrupts.CPU23.LOC:Local_timer_interrupts 725.00 ± 6% +353.0% 3284 interrupts.CPU23.RES:Rescheduling_interrupts 212540 +10.4% 234711 interrupts.CPU24.LOC:Local_timer_interrupts 796.75 ± 8% +307.1% 3243 interrupts.CPU24.RES:Rescheduling_interrupts 760.25 ± 7% +323.9% 3222 interrupts.CPU25.RES:Rescheduling_interrupts 212521 +10.3% 234433 interrupts.CPU26.LOC:Local_timer_interrupts 731.00 ± 10% +348.1% 3275 ± 2% interrupts.CPU26.RES:Rescheduling_interrupts 1647 ± 65% +391.9% 8102 interrupts.CPU27.NMI:Non-maskable_interrupts 1647 ± 65% +391.9% 8102 interrupts.CPU27.PMI:Performance_monitoring_interrupts 696.75 ± 9% +364.1% 3233 ± 2% interrupts.CPU27.RES:Rescheduling_interrupts 212335 +10.5% 234699 interrupts.CPU28.LOC:Local_timer_interrupts 859.25 ± 10% +274.9% 3221 ± 3% interrupts.CPU28.RES:Rescheduling_interrupts 724.50 ± 10% +344.8% 3222 ± 3% interrupts.CPU29.RES:Rescheduling_interrupts 212478 +10.5% 234859 interrupts.CPU3.LOC:Local_timer_interrupts 725.75 ± 7% +369.2% 3405 ± 2% interrupts.CPU3.RES:Rescheduling_interrupts 212297 +10.4% 234380 interrupts.CPU30.LOC:Local_timer_interrupts 653.00 ± 4% +406.5% 3307 interrupts.CPU30.RES:Rescheduling_interrupts 716.00 ± 12% +356.7% 3270 interrupts.CPU31.RES:Rescheduling_interrupts 212377 +10.4% 234446 interrupts.CPU32.LOC:Local_timer_interrupts 739.25 ± 16% +338.4% 3240 interrupts.CPU32.RES:Rescheduling_interrupts 773.50 ± 5% +318.3% 3235 interrupts.CPU33.RES:Rescheduling_interrupts 212097 +10.5% 234446 interrupts.CPU34.LOC:Local_timer_interrupts 807.25 ± 17% +311.5% 3321 interrupts.CPU34.RES:Rescheduling_interrupts 1874 ± 65% +117.5% 4075 interrupts.CPU35.NMI:Non-maskable_interrupts 1874 ± 65% +117.5% 4075 interrupts.CPU35.PMI:Performance_monitoring_interrupts 704.00 ± 10% +363.1% 3260 ± 2% interrupts.CPU35.RES:Rescheduling_interrupts 765.75 ± 11% +326.7% 3267 interrupts.CPU36.RES:Rescheduling_interrupts 2066 ± 43% +96.7% 4065 interrupts.CPU37.NMI:Non-maskable_interrupts 2066 ± 43% +96.7% 4065 interrupts.CPU37.PMI:Performance_monitoring_interrupts 710.75 ± 14% +368.9% 3332 ± 4% interrupts.CPU37.RES:Rescheduling_interrupts 212185 +10.6% 234607 interrupts.CPU38.LOC:Local_timer_interrupts 1126 ±108% +381.1% 5416 ± 35% interrupts.CPU38.NMI:Non-maskable_interrupts 1126 ±108% +381.1% 5416 ± 35% interrupts.CPU38.PMI:Performance_monitoring_interrupts 690.00 ± 10% +376.4% 3287 ± 2% interrupts.CPU38.RES:Rescheduling_interrupts 212183 +10.5% 234362 interrupts.CPU39.LOC:Local_timer_interrupts 693.00 ± 9% +360.0% 3188 interrupts.CPU39.RES:Rescheduling_interrupts 1215 ± 61% +166.0% 3232 interrupts.CPU4.RES:Rescheduling_interrupts 794.25 ± 10% +308.6% 3245 interrupts.CPU5.RES:Rescheduling_interrupts 212385 +10.3% 234361 interrupts.CPU6.LOC:Local_timer_interrupts 1500 ± 57% +120.6% 3311 interrupts.CPU6.RES:Rescheduling_interrupts 790.50 ± 13% +314.7% 3278 ± 3% interrupts.CPU7.RES:Rescheduling_interrupts 212494 +10.4% 234598 interrupts.CPU8.LOC:Local_timer_interrupts 690.00 ± 12% +359.7% 3171 interrupts.CPU8.RES:Rescheduling_interrupts 651.50 ± 7% +404.6% 3287 interrupts.CPU9.RES:Rescheduling_interrupts 8500355 +10.3% 9379328 interrupts.LOC:Local_timer_interrupts 53220 ± 11% +172.2% 144867 ± 7% interrupts.NMI:Non-maskable_interrupts 53220 ± 11% +172.2% 144867 ± 7% interrupts.PMI:Performance_monitoring_interrupts 32058 ± 3% +319.0% 134339 interrupts.RES:Rescheduling_interrupts 346.75 ± 8% -59.3% 141.00 ± 8% interrupts.TLB:TLB_shootdowns 37.49 -23.8 13.67 perf-profile.calltrace.cycles-pp.write 32.13 ± 2% -20.3 11.82 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.write 31.88 ± 2% -20.2 11.73 perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 22.34 ± 6% -19.7 2.63 ± 13% perf-profile.calltrace.cycles-pp.secondary_startup_64 30.70 ± 2% -19.3 11.36 perf-profile.calltrace.cycles-pp.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 21.87 ± 7% -19.3 2.55 ± 11% perf-profile.calltrace.cycles-pp.cpu_startup_entry.start_secondary.secondary_startup_64 21.87 ± 7% -19.3 2.55 ± 11% perf-profile.calltrace.cycles-pp.start_secondary.secondary_startup_64 21.87 ± 7% -19.3 2.55 ± 11% perf-profile.calltrace.cycles-pp.do_idle.cpu_startup_entry.start_secondary.secondary_startup_64 21.43 ± 7% -18.9 2.50 ± 11% perf-profile.calltrace.cycles-pp.cpuidle_enter_state.do_idle.cpu_startup_entry.start_secondary.secondary_startup_64 29.87 -18.8 11.06 perf-profile.calltrace.cycles-pp.vfs_write.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 20.88 ± 7% -18.4 2.46 ± 11% perf-profile.calltrace.cycles-pp.intel_idle.cpuidle_enter_state.do_idle.cpu_startup_entry.start_secondary 26.39 -16.7 9.72 perf-profile.calltrace.cycles-pp.new_sync_write.vfs_write.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe 24.86 ± 2% -15.6 9.30 perf-profile.calltrace.cycles-pp.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write.do_syscall_64 20.87 -12.9 7.93 perf-profile.calltrace.cycles-pp.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write 20.72 -12.9 7.87 perf-profile.calltrace.cycles-pp.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write.vfs_write 15.79 -9.8 5.98 perf-profile.calltrace.cycles-pp.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write 8.44 -5.6 2.86 perf-profile.calltrace.cycles-pp.lseek64 8.52 ± 2% -5.3 3.19 perf-profile.calltrace.cycles-pp.iomap_write_begin.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write 6.07 ± 3% -3.9 2.14 perf-profile.calltrace.cycles-pp.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor.iomap_apply.iomap_file_buffered_write 5.83 ± 3% -3.8 2.04 ± 2% perf-profile.calltrace.cycles-pp.pagecache_get_page.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor.iomap_apply 4.17 ± 3% -2.6 1.52 perf-profile.calltrace.cycles-pp.close 4.11 ± 3% -2.6 1.50 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.close 4.11 ± 3% -2.6 1.50 perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.close 4.09 ± 3% -2.6 1.50 perf-profile.calltrace.cycles-pp.exit_to_usermode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.close 4.08 ± 3% -2.6 1.49 perf-profile.calltrace.cycles-pp.task_work_run.exit_to_usermode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe.close 4.06 ± 3% -2.6 1.48 perf-profile.calltrace.cycles-pp.__fput.task_work_run.exit_to_usermode_loop.do_syscall_64.entry_SYSCALL_64_after_hwframe 3.88 ± 3% -2.5 1.43 perf-profile.calltrace.cycles-pp.dput.__fput.task_work_run.exit_to_usermode_loop.do_syscall_64 3.87 ± 3% -2.4 1.42 perf-profile.calltrace.cycles-pp.dentry_kill.dput.__fput.task_work_run.exit_to_usermode_loop 3.87 ± 3% -2.4 1.42 perf-profile.calltrace.cycles-pp.__dentry_kill.dentry_kill.dput.__fput.task_work_run 3.64 ± 3% -2.2 1.40 perf-profile.calltrace.cycles-pp.xfs_file_iomap_begin.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write 3.44 ± 2% -2.2 1.23 ± 3% perf-profile.calltrace.cycles-pp.iomap_write_end.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write 3.11 ± 4% -2.1 1.06 ± 3% perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.lseek64 2.89 ± 5% -1.9 0.97 ± 4% perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.lseek64 3.09 ± 2% -1.9 1.19 perf-profile.calltrace.cycles-pp.xfs_file_iomap_begin_delay.xfs_file_iomap_begin.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write 2.99 ± 2% -1.9 1.10 perf-profile.calltrace.cycles-pp.evict.__dentry_kill.dentry_kill.dput.__fput 2.97 ± 2% -1.9 1.09 perf-profile.calltrace.cycles-pp.truncate_inode_pages_range.evict.__dentry_kill.dentry_kill.dput 2.81 -1.9 0.94 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64.lseek64 2.78 ± 3% -1.8 0.96 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64.read 2.78 ± 2% -1.8 0.97 ± 3% perf-profile.calltrace.cycles-pp.entry_SYSCALL_64.write 2.39 ± 3% -1.6 0.80 ± 3% perf-profile.calltrace.cycles-pp.add_to_page_cache_lru.pagecache_get_page.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor 2.32 ± 3% -1.6 0.76 ± 5% perf-profile.calltrace.cycles-pp.xfs_file_aio_write_checks.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write 2.29 -1.5 0.78 ± 2% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.write 2.28 -1.5 0.78 ± 2% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.read 1.98 ± 3% -1.4 0.56 ± 3% perf-profile.calltrace.cycles-pp.creat 1.96 ± 3% -1.4 0.54 ± 3% perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.creat 1.96 ± 3% -1.4 0.54 ± 3% perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.creat 1.95 ± 3% -1.4 0.54 ± 3% perf-profile.calltrace.cycles-pp.do_sys_open.do_syscall_64.entry_SYSCALL_64_after_hwframe.creat 1.93 ± 3% -1.4 0.54 ± 4% perf-profile.calltrace.cycles-pp.do_filp_open.do_sys_open.do_syscall_64.entry_SYSCALL_64_after_hwframe.creat 1.92 ± 3% -1.4 0.53 ± 4% perf-profile.calltrace.cycles-pp.path_openat.do_filp_open.do_sys_open.do_syscall_64.entry_SYSCALL_64_after_hwframe 2.09 ± 2% -1.4 0.72 ± 2% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.lseek64 1.81 ± 7% -1.2 0.60 ± 5% perf-profile.calltrace.cycles-pp.ksys_lseek.do_syscall_64.entry_SYSCALL_64_after_hwframe.lseek64 2.60 ± 5% -1.2 1.41 ± 2% perf-profile.calltrace.cycles-pp.copyout.copy_page_to_iter.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 2.57 ± 5% -1.2 1.39 ± 2% perf-profile.calltrace.cycles-pp.copy_user_enhanced_fast_string.copyout.copy_page_to_iter.generic_file_read_iter.xfs_file_buffered_aio_read 2.04 -1.2 0.88 perf-profile.calltrace.cycles-pp.iomap_read_page_sync.iomap_write_begin.iomap_write_actor.iomap_apply.iomap_file_buffered_write 1.94 ± 2% -1.1 0.81 perf-profile.calltrace.cycles-pp.iov_iter_copy_from_user_atomic.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write 1.70 ± 3% -1.0 0.67 ± 3% perf-profile.calltrace.cycles-pp.security_file_permission.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe 1.48 ± 3% -1.0 0.52 perf-profile.calltrace.cycles-pp.__alloc_pages_nodemask.pagecache_get_page.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor 1.62 ± 2% -1.0 0.67 perf-profile.calltrace.cycles-pp.copyin.iov_iter_copy_from_user_atomic.iomap_write_actor.iomap_apply.iomap_file_buffered_write 1.48 ± 2% -0.9 0.53 ± 4% perf-profile.calltrace.cycles-pp.iomap_set_page_dirty.iomap_write_end.iomap_write_actor.iomap_apply.iomap_file_buffered_write 1.55 ± 3% -0.9 0.64 perf-profile.calltrace.cycles-pp.copy_user_enhanced_fast_string.copyin.iov_iter_copy_from_user_atomic.iomap_write_actor.iomap_apply 1.46 ± 5% -0.9 0.56 perf-profile.calltrace.cycles-pp.security_file_permission.vfs_write.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe 1.49 ± 2% -0.8 0.66 perf-profile.calltrace.cycles-pp.memset_erms.iomap_read_page_sync.iomap_write_begin.iomap_write_actor.iomap_apply 0.77 ± 8% -0.2 0.59 perf-profile.calltrace.cycles-pp.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 0.00 +1.0 1.01 perf-profile.calltrace.cycles-pp.rcu_all_qs._cond_resched.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 0.00 +1.9 1.90 perf-profile.calltrace.cycles-pp._cond_resched.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 3.44 ± 5% +3.1 6.51 perf-profile.calltrace.cycles-pp.copy_page_to_iter.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 1.94 ± 3% +3.4 5.34 perf-profile.calltrace.cycles-pp.mark_page_accessed.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 0.00 +5.5 5.50 ± 3% perf-profile.calltrace.cycles-pp.xas_start.xas_load.find_get_entry.pagecache_get_page.generic_file_read_iter 0.00 +6.2 6.23 perf-profile.calltrace.cycles-pp.___might_sleep.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 0.75 ± 3% +12.5 13.26 perf-profile.calltrace.cycles-pp.xas_load.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read 1.88 ± 2% +29.5 31.36 perf-profile.calltrace.cycles-pp.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 1.98 ± 2% +33.0 34.98 perf-profile.calltrace.cycles-pp.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 22.57 ± 2% +55.3 77.91 perf-profile.calltrace.cycles-pp.read 17.07 +58.9 75.99 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.read 16.81 ± 2% +59.1 75.89 perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 15.73 ± 2% +59.8 75.53 perf-profile.calltrace.cycles-pp.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 14.88 ± 2% +60.4 75.25 perf-profile.calltrace.cycles-pp.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 11.85 ± 2% +62.3 74.12 perf-profile.calltrace.cycles-pp.new_sync_read.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe 11.49 ± 2% +62.5 73.98 perf-profile.calltrace.cycles-pp.xfs_file_read_iter.new_sync_read.vfs_read.ksys_read.do_syscall_64 9.23 ± 2% +62.6 71.83 perf-profile.calltrace.cycles-pp.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read 10.26 ± 2% +63.3 73.60 perf-profile.calltrace.cycles-pp.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read.ksys_read 17585 ± 2% -22.6% 13604 ± 3% softirqs.CPU0.RCU 18027 ± 2% -31.3% 12389 ± 2% softirqs.CPU0.SCHED 17656 ± 3% -26.0% 13065 ± 2% softirqs.CPU1.RCU 14588 ± 2% -37.4% 9138 softirqs.CPU1.SCHED 17689 ± 6% -28.2% 12698 ± 9% softirqs.CPU10.RCU 14546 -43.2% 8264 ± 3% softirqs.CPU10.SCHED 16926 ± 4% -25.2% 12664 ± 12% softirqs.CPU11.RCU 14657 -36.3% 9333 ± 5% softirqs.CPU11.SCHED 19656 ± 10% -26.4% 14468 ± 20% softirqs.CPU12.RCU 15085 ± 3% -39.6% 9112 softirqs.CPU12.SCHED 45423 ± 3% +12.4% 51043 ± 3% softirqs.CPU12.TIMER 17215 ± 7% -23.8% 13114 ± 5% softirqs.CPU13.RCU 14710 -39.1% 8960 ± 3% softirqs.CPU13.SCHED 17320 ± 4% -28.2% 12431 ± 2% softirqs.CPU14.RCU 14956 -37.3% 9380 ± 2% softirqs.CPU14.SCHED 18506 ± 6% -29.2% 13108 ± 4% softirqs.CPU15.RCU 14702 -38.8% 8995 ± 2% softirqs.CPU15.SCHED 17497 ± 6% -31.1% 12060 ± 4% softirqs.CPU16.RCU 14987 -39.0% 9144 ± 4% softirqs.CPU16.SCHED 44555 ± 2% +14.0% 50798 ± 3% softirqs.CPU16.TIMER 17239 ± 6% -26.2% 12720 ± 4% softirqs.CPU17.RCU 14707 -39.0% 8968 ± 2% softirqs.CPU17.SCHED 17035 ± 5% -24.4% 12872 ± 4% softirqs.CPU18.RCU 14862 -39.0% 9065 softirqs.CPU18.SCHED 44056 ± 2% +13.3% 49898 softirqs.CPU18.TIMER 17108 ± 6% -29.4% 12077 ± 4% softirqs.CPU19.RCU 14789 -39.6% 8934 ± 2% softirqs.CPU19.SCHED 19187 ± 8% -22.8% 14803 ± 15% softirqs.CPU2.RCU 15056 ± 6% -37.8% 9368 ± 2% softirqs.CPU2.SCHED 45404 ± 5% +13.9% 51724 ± 4% softirqs.CPU2.TIMER 17685 ± 5% -28.2% 12690 ± 9% softirqs.CPU20.RCU 15162 ± 5% -41.0% 8951 softirqs.CPU20.SCHED 17396 ± 5% -30.1% 12152 ± 11% softirqs.CPU21.RCU 14572 -38.6% 8943 ± 2% softirqs.CPU21.SCHED 17193 ± 5% -28.8% 12242 ± 7% softirqs.CPU22.RCU 15052 -40.9% 8899 ± 3% softirqs.CPU22.SCHED 44869 ± 3% +22.3% 54895 ± 15% softirqs.CPU22.TIMER 17908 ± 9% -30.2% 12494 ± 5% softirqs.CPU23.RCU 14659 -39.0% 8946 ± 3% softirqs.CPU23.SCHED 18382 ± 10% -30.9% 12706 ± 2% softirqs.CPU24.RCU 14776 -38.7% 9061 softirqs.CPU24.SCHED 44675 ± 2% +12.5% 50240 softirqs.CPU24.TIMER 17003 ± 3% -22.1% 13251 ± 11% softirqs.CPU25.RCU 14698 -39.0% 8973 ± 4% softirqs.CPU25.SCHED 18396 ± 10% -36.1% 11747 ± 3% softirqs.CPU26.RCU 14924 ± 2% -40.0% 8949 ± 3% softirqs.CPU26.SCHED 44944 +16.4% 52321 ± 4% softirqs.CPU26.TIMER 17076 ± 5% -26.1% 12614 ± 6% softirqs.CPU27.RCU 14680 -38.8% 8982 ± 3% softirqs.CPU27.SCHED 43977 ± 2% +10.7% 48691 softirqs.CPU27.TIMER 16848 ± 3% -27.6% 12203 ± 5% softirqs.CPU28.RCU 14838 ± 3% -38.3% 9156 ± 2% softirqs.CPU28.SCHED 44188 +12.3% 49639 softirqs.CPU28.TIMER 17635 ± 8% -24.4% 13339 ± 7% softirqs.CPU29.RCU 14668 -38.6% 9004 ± 2% softirqs.CPU29.SCHED 16857 ± 3% -21.4% 13243 ± 7% softirqs.CPU3.RCU 14869 -38.8% 9098 softirqs.CPU3.SCHED 17771 ± 8% -29.0% 12612 ± 10% softirqs.CPU30.RCU 14272 ± 3% -41.1% 8401 ± 4% softirqs.CPU30.SCHED 42106 +11.9% 47104 softirqs.CPU30.TIMER 17493 ± 6% -30.5% 12163 ± 7% softirqs.CPU31.RCU 14723 -38.7% 9022 ± 2% softirqs.CPU31.SCHED 17607 ± 20% -32.7% 11841 ± 26% softirqs.CPU32.RCU 15051 ± 2% -40.2% 8995 softirqs.CPU32.SCHED 13429 ± 3% -28.4% 9620 ± 4% softirqs.CPU33.RCU 14633 -37.3% 9169 ± 2% softirqs.CPU33.SCHED 14829 ± 8% -35.2% 9614 softirqs.CPU34.RCU 14929 -39.3% 9068 softirqs.CPU34.SCHED 45384 ± 4% +9.7% 49801 ± 2% softirqs.CPU34.TIMER 13817 ± 9% -24.8% 10384 ± 8% softirqs.CPU35.RCU 14756 -39.6% 8914 ± 2% softirqs.CPU35.SCHED 13609 ± 2% -22.7% 10525 ± 9% softirqs.CPU36.RCU 14906 ± 2% -40.1% 8927 ± 2% softirqs.CPU36.SCHED 44085 +33.3% 58762 ± 21% softirqs.CPU36.TIMER 14308 ± 14% -26.3% 10550 ± 12% softirqs.CPU37.RCU 14712 -38.6% 9029 softirqs.CPU37.SCHED 15404 ± 8% -30.2% 10753 ± 9% softirqs.CPU38.RCU 14757 -39.3% 8963 softirqs.CPU38.SCHED 13292 ± 4% -22.4% 10309 ± 10% softirqs.CPU39.RCU 14643 ± 2% -39.2% 8901 softirqs.CPU39.SCHED 17513 ± 8% -27.8% 12646 ± 3% softirqs.CPU4.RCU 15099 ± 3% -40.3% 9020 softirqs.CPU4.SCHED 17507 ± 8% -27.9% 12614 ± 3% softirqs.CPU5.RCU 14752 -39.2% 8975 ± 3% softirqs.CPU5.SCHED 17584 ± 5% -31.6% 12025 ± 2% softirqs.CPU6.RCU 15115 ± 2% -42.0% 8760 ± 3% softirqs.CPU6.SCHED 18973 ± 3% -29.0% 13480 ± 3% softirqs.CPU7.RCU 14761 -39.3% 8957 ± 3% softirqs.CPU7.SCHED 17096 ± 4% -28.8% 12176 softirqs.CPU8.RCU 14989 ± 2% -40.5% 8926 softirqs.CPU8.SCHED 17209 ± 7% -30.8% 11908 ± 4% softirqs.CPU9.RCU 14720 -38.3% 9076 softirqs.CPU9.SCHED 680461 ± 4% -27.8% 491610 ± 3% softirqs.RCU 595414 -39.0% 363137 softirqs.SCHED aim7.jobs-per-min 180000 +-+----------------------------------------------------------------+ | : : : : + O : : : : : : + | 160000 O-O O O O O O : O O O O : O O O O O O O : | 140000 +-+ : :: : : : :: : : : : | |: : : : : : : : : : : : : : : : : | 120000 +-+: : : : : : : : : : : : : : : : | 100000 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 80000 +-+: : : : : : : : : : : : : : : : | 60000 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 40000 +-+ : : : :: :: : : : : : : | 20000 +-+ : : : : : : : : : : : | | : : : : : : : : : : : | 0 +-+----O--------O---O-------------O-------O--------O---------------+ aim7.time.user_time 350 +-+-------------------------------------------------------------------+ | + + + +. .+ + + + +.+.+..+.+ +.+. .+.| 300 +-+ : : : + : : : : : : : +. | | : : : : : : : : : : : | 250 +-+: :: : : : : : :: : : : | |: : : : : : : : : : : : : : : : : | 200 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 150 O-O :O :O :O:O: : : : : : : : : : : : | |: : : : : : : O O :O:O:O O: :O: O:O : O O O O: : | 100 +-+ : : : : : : : : : : : : : : : : | | : : :: :: :: : : :: : : :: | 50 +-+ : : : : : : : : : : : | | : : : : : : : : : : : | 0 +-+----O--------O----O-------------O--------O---------O---------------+ aim7.time.system_time 4000 +-+---------O-O----------O--O----------O-O----O-O--O---O-------------+ O O O O O O O O O | 3500 +-+ | 3000 +-+ | | | 2500 +-+ | | + + + +..+.+ + + + +.+..+.+.+ +.+.+..+.| 2000 +-+ : : : : : : : : : : | | :: :: :: : : : : : : :: : : : | 1500 +-+: : : : : : : : : : : : : : : : | 1000 +-+ : : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 500 +-+ : : : : :: :: : : :: : : : : | | : : : : : : : : : : : | 0 +-+----O--------O----O-------------O--------O--------O---------------+ aim7.time.elapsed_time 120 +-+---------O-O-----------O-O-----------O-O----O-O-O----O-------------+ O O O O O O O O O | 100 +-+ + + +.+.+ + + + +.+.+..+.+ +.+.+..+.| | : : : : : : : : : : : | | :: :: : : : : : : : : : | 80 +-+: :: :: : : :: :: : : : : : | |: : : : : : : : : : : : : : : : : | 60 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 40 +-+ : : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | |: : : : : :: : : : : :: : : :: | 20 +-+ : : : :: : : : :: : : :: | | : : : : : : : : : : : | 0 +-+----O--------O----O-------------O--------O---------O---------------+ aim7.time.elapsed_time.max 120 +-+---------O-O-----------O-O-----------O-O----O-O-O----O-------------+ O O O O O O O O O | 100 +-+ + + +.+.+ + + + +.+.+..+.+ +.+.+..+.| | : : : : : : : : : : : | | :: :: : : : : : : : : : | 80 +-+: :: :: : : :: :: : : : : : | |: : : : : : : : : : : : : : : : : | 60 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 40 +-+ : : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | |: : : : : :: : : : : :: : : :: | 20 +-+ : : : :: : : : :: : : :: | | : : : : : : : : : : : | 0 +-+----O--------O----O-------------O--------O---------O---------------+ aim7.time.voluntary_context_switches 1.2e+06 +-+---------------------------------------------------------------+ | + + + +.+.+ + + + +.+.+..+.+ +.+..+.+.| 1e+06 +-+ : : : : : : : : : : | | : : : : : : : : : : : | | : : : : : :: : :: : : : | 800000 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | 600000 O-O:O :O: : : : O: : : O O: :O:O: : O : : | |: : : :O:O: : O :O:O : : : : :O :O O O: : | 400000 +-+: : : : : : : : : : : : : : : : | |: : : : : : : : : : : : : : : : : | | : : : :: : : : : : : : | 200000 +-+ : : : : : : : : : : : | | : : : : : : : : : : : | 0 +-+----O-------O----O------------O--------O--------O--------------+ aim7.time.involuntary_context_switches 160000 +-+------------------------O---------------------------------------+ O O O O O O O O O O O O O O O O O O | 140000 +-+ | 120000 +-+ | | | 100000 +-+ | | | 80000 +-+ | | | 60000 +-+ | 40000 +-+ | | | 20000 +-+ | |.+. .+. .+.. .+.+.+.. .+. .+. .+. .+.+.+.+..+. .+.+..+.+.| 0 +-+----O--------O---O-------------O-------O--------O---------------+ [*] bisect-good sample [O] bisect-bad sample *************************************************************************************************** lkp-ivb-d02: 4 threads Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz with 8G memory ========================================================================================= compiler/cpufreq_governor/kconfig/rootfs/runtime/tbox_group/test/testcase/ucode: gcc-7/performance/x86_64-rhel-7.6/debian-x86_64-2018-04-03.cgz/300s/lkp-ivb-d02/lru-file-readonce/vm-scalability/0x20 commit: 8e22ba96d4 (" RISC-V Patches for 5.1-rc4") fa3fe73bed ("xfs: reduce ilock contention on buffered randrw workload") 8e22ba96d44c4ad5 fa3fe73bed17967cb623461b166 ---------------- --------------------------- fail:runs %reproduction fail:runs | | | :4 50% 2:4 dmesg.WARNING:at#for_ip_swapgs_restore_regs_and_return_to_usermode/0x :4 50% 2:4 dmesg.WARNING:stack_recursion %stddev %change %stddev \ | \ 1213560 -5.2% 1150446 vm-scalability.median 4826960 -5.3% 4569635 vm-scalability.throughput 3737 -2.1% 3658 vm-scalability.time.maximum_resident_set_size 315.50 +1.4% 320.00 vm-scalability.time.percent_of_cpu_this_job_got 854.51 +2.3% 874.06 vm-scalability.time.system_time 103.13 -6.1% 96.80 vm-scalability.time.user_time 1.448e+09 -5.3% 1.371e+09 vm-scalability.workload 97466 ± 3% -19.6% 78394 ± 18% softirqs.CPU3.RCU 735.00 ± 9% -18.2% 601.33 ± 3% slabinfo.kmalloc-rcl-96.active_objs 735.00 ± 9% -18.2% 601.33 ± 3% slabinfo.kmalloc-rcl-96.num_objs 7589 +1.9% 7732 interrupts.CAL:Function_call_interrupts 756810 ± 6% -10.5% 677379 interrupts.CPU2.LOC:Local_timer_interrupts 2172 ± 13% -36.1% 1387 ± 28% interrupts.CPU3.CAL:Function_call_interrupts 701245 ± 6% +20.1% 842502 ± 12% interrupts.CPU3.LOC:Local_timer_interrupts -17569 -72.7% -4788 sched_debug.cfs_rq:/.spread0.min 807.29 ± 3% +11.4% 899.61 ± 2% sched_debug.cfs_rq:/.util_avg.min 172.38 ± 15% -35.8% 110.68 ± 16% sched_debug.cfs_rq:/.util_avg.stddev 186.29 ± 5% -4.8% 177.39 ± 3% sched_debug.cpu.cpu_load[3].min 3.96 ± 14% -24.2% 3.00 sched_debug.cpu.nr_running.max 1.17 ± 19% -35.4% 0.76 sched_debug.cpu.nr_running.stddev 9.50 ± 39% +175.4% 26.17 ± 44% sched_debug.cpu.nr_uninterruptible.max -12.37 +125.4% -27.89 sched_debug.cpu.nr_uninterruptible.min 8.35 ± 24% +154.7% 21.27 ± 41% sched_debug.cpu.nr_uninterruptible.stddev 5224 ± 4% -26.6% 3835 ± 13% proc-vmstat.compact_daemon_wake 18209 ± 4% +11.0% 20204 proc-vmstat.kswapd_low_wmark_hit_quickly 3.624e+08 -5.3% 3.431e+08 proc-vmstat.numa_hit 3.624e+08 -5.3% 3.431e+08 proc-vmstat.numa_local 18216 ± 4% +11.0% 20216 proc-vmstat.pageoutrun 1.923e+08 -5.5% 1.818e+08 proc-vmstat.pgalloc_dma32 1.704e+08 -5.2% 1.615e+08 proc-vmstat.pgalloc_normal 3.628e+08 -5.3% 3.435e+08 proc-vmstat.pgfree 3.604e+08 -5.4% 3.411e+08 proc-vmstat.pgscan_kswapd 3.604e+08 -5.4% 3.411e+08 proc-vmstat.pgsteal_kswapd 5729332 -5.9% 5391641 proc-vmstat.slabs_scanned 2593384 -6.0% 2437353 proc-vmstat.workingset_nodereclaim 32.26 ± 7% -4.1 28.21 ± 5% perf-profile.calltrace.cycles-pp.ondemand_readahead.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 32.20 ± 7% -4.0 28.17 ± 5% perf-profile.calltrace.cycles-pp.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 23.30 ± 8% -3.0 20.35 ± 5% perf-profile.calltrace.cycles-pp.read_pages.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter.xfs_file_buffered_aio_read 23.22 ± 8% -2.9 20.27 ± 5% perf-profile.calltrace.cycles-pp.iomap_readpages.read_pages.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter 23.16 ± 8% -2.9 20.23 ± 5% perf-profile.calltrace.cycles-pp.iomap_apply.iomap_readpages.read_pages.__do_page_cache_readahead.ondemand_readahead 22.79 ± 8% -2.9 19.87 ± 5% perf-profile.calltrace.cycles-pp.iomap_readpages_actor.iomap_apply.iomap_readpages.read_pages.__do_page_cache_readahead 10.41 ± 8% -1.4 8.97 ± 2% perf-profile.calltrace.cycles-pp.iomap_readpage_actor.iomap_readpages_actor.iomap_apply.iomap_readpages.read_pages 11.40 ± 8% -1.3 10.08 ± 7% perf-profile.calltrace.cycles-pp.add_to_page_cache_lru.iomap_readpages_actor.iomap_apply.iomap_readpages.read_pages 7.92 ± 8% -1.1 6.82 ± 2% perf-profile.calltrace.cycles-pp.memset_erms.iomap_readpage_actor.iomap_readpages_actor.iomap_apply.iomap_readpages 6.88 ± 7% -0.7 6.15 ± 8% perf-profile.calltrace.cycles-pp.__add_to_page_cache_locked.add_to_page_cache_lru.iomap_readpages_actor.iomap_apply.iomap_readpages 6.16 ± 8% -0.6 5.53 ± 2% perf-profile.calltrace.cycles-pp.__alloc_pages_nodemask.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter.xfs_file_buffered_aio_read 3.75 ± 8% -0.4 3.32 ± 7% perf-profile.calltrace.cycles-pp.entry_SYSCALL_64.read 2.96 ± 11% -0.4 2.57 ± 5% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.write 2.97 ± 6% -0.4 2.58 ± 8% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.read 1.49 ± 11% -0.3 1.19 ± 2% perf-profile.calltrace.cycles-pp.iomap_set_range_uptodate.iomap_readpage_actor.iomap_readpages_actor.iomap_apply.iomap_readpages 0.63 ± 4% -0.3 0.36 ± 70% perf-profile.calltrace.cycles-pp.mark_page_accessed.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 1.24 ± 9% -0.3 0.98 ± 4% perf-profile.calltrace.cycles-pp.__list_del_entry_valid.get_page_from_freelist.__alloc_pages_nodemask.__do_page_cache_readahead.ondemand_readahead 0.62 ± 7% -0.2 0.38 ± 71% perf-profile.calltrace.cycles-pp.__fget_light.__fdget_pos.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe 1.76 ± 6% -0.2 1.52 ± 11% perf-profile.calltrace.cycles-pp.selinux_file_permission.security_file_permission.vfs_write.ksys_write.do_syscall_64 1.65 ± 4% -0.2 1.42 ± 7% perf-profile.calltrace.cycles-pp.xa_load.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter.xfs_file_buffered_aio_read 1.46 ± 4% -0.2 1.24 ± 6% perf-profile.calltrace.cycles-pp.xas_load.xa_load.__do_page_cache_readahead.ondemand_readahead.generic_file_read_iter 0.73 ± 9% -0.1 0.63 ± 7% perf-profile.calltrace.cycles-pp._raw_spin_lock_irq.__add_to_page_cache_locked.add_to_page_cache_lru.iomap_readpages_actor.iomap_apply 0.58 ± 9% +0.4 0.97 ± 13% perf-profile.calltrace.cycles-pp.current_time.atime_needs_update.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read 0.93 ± 6% +0.7 1.63 ± 12% perf-profile.calltrace.cycles-pp.atime_needs_update.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 2.69 ± 6% +0.8 3.51 ± 7% perf-profile.calltrace.cycles-pp.xas_load.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read 1.09 ± 6% +0.9 1.94 ± 13% perf-profile.calltrace.cycles-pp.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 4.15 ± 6% +1.2 5.40 ± 7% perf-profile.calltrace.cycles-pp.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 4.29 ± 6% +1.4 5.69 ± 8% perf-profile.calltrace.cycles-pp.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 17.08 -9.4% 15.47 ± 2% perf-stat.i.MPKI 1.638e+09 +4.2% 1.706e+09 perf-stat.i.branch-instructions 0.94 ± 2% -0.1 0.86 perf-stat.i.branch-miss-rate% 15189313 ± 3% -4.3% 14541135 perf-stat.i.branch-misses 60.39 -0.4 59.95 perf-stat.i.cache-miss-rate% 84514861 -6.2% 79245867 ± 2% perf-stat.i.cache-misses 1.393e+08 -5.7% 1.314e+08 perf-stat.i.cache-references 1.56 -3.8% 1.50 perf-stat.i.cpi 76.62 -2.8% 74.44 perf-stat.i.cpu-migrations 166.97 +7.7% 179.74 perf-stat.i.cycles-between-cache-misses 1.55 +0.2 1.71 perf-stat.i.dTLB-load-miss-rate% 40318360 +13.9% 45905767 perf-stat.i.dTLB-load-misses 2.554e+09 +3.0% 2.632e+09 perf-stat.i.dTLB-loads 0.07 ± 2% +0.0 0.08 ± 6% perf-stat.i.dTLB-store-miss-rate% 1413447 ± 2% +14.8% 1622498 ± 5% perf-stat.i.dTLB-store-misses 8.311e+09 +3.8% 8.629e+09 perf-stat.i.instructions 0.65 +3.7% 0.67 perf-stat.i.ipc 16.76 -9.2% 15.23 ± 2% perf-stat.overall.MPKI 0.93 ± 3% -0.1 0.85 perf-stat.overall.branch-miss-rate% 60.65 -0.3 60.31 perf-stat.overall.cache-miss-rate% 1.55 -3.7% 1.49 perf-stat.overall.cpi 152.55 +6.7% 162.72 perf-stat.overall.cycles-between-cache-misses 1.55 +0.2 1.71 perf-stat.overall.dTLB-load-miss-rate% 0.07 ± 2% +0.0 0.08 ± 6% perf-stat.overall.dTLB-store-miss-rate% 0.64 +3.8% 0.67 perf-stat.overall.ipc 1744 +9.6% 1911 perf-stat.overall.path-length 1.633e+09 +4.2% 1.702e+09 perf-stat.ps.branch-instructions 15141912 ± 3% -4.2% 14504616 perf-stat.ps.branch-misses 84251986 -6.2% 79053575 perf-stat.ps.cache-misses 1.389e+08 -5.6% 1.311e+08 perf-stat.ps.cache-references 76.39 -2.8% 74.26 perf-stat.ps.cpu-migrations 40194141 +13.9% 45794346 perf-stat.ps.dTLB-load-misses 2.547e+09 +3.1% 2.625e+09 perf-stat.ps.dTLB-loads 1409206 ± 2% +14.9% 1618569 ± 5% perf-stat.ps.dTLB-store-misses 8.286e+09 +3.9% 8.608e+09 perf-stat.ps.instructions 2.525e+12 +3.8% 2.621e+12 perf-stat.total.instructions *************************************************************************************************** lkp-ivb-ep01: 40 threads Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with 384G memory ========================================================================================= compiler/cpufreq_governor/disk/fs/kconfig/load/md/rootfs/tbox_group/test/testcase: gcc-7/performance/4BRD_12G/xfs/x86_64-rhel-7.6/3000/RAID1/debian-x86_64-2018-04-03.cgz/lkp-ivb-ep01/disk_cp/aim7 commit: 8e22ba96d4 (" RISC-V Patches for 5.1-rc4") fa3fe73bed ("xfs: reduce ilock contention on buffered randrw workload") 8e22ba96d44c4ad5 fa3fe73bed17967cb623461b166 ---------------- --------------------------- fail:runs %reproduction fail:runs | | | 1:4 -25% :4 dmesg.WARNING:at#for_ip_interrupt_entry/0x %stddev %change %stddev \ | \ 230947 -79.4% 47688 aim7.jobs-per-min 78.62 +380.5% 377.76 aim7.time.elapsed_time 78.62 +380.5% 377.76 aim7.time.elapsed_time.max 89921 +604.3% 633289 ± 2% aim7.time.involuntary_context_switches 150384 ± 2% +35.4% 203653 aim7.time.minor_page_faults 2333 +518.7% 14439 aim7.time.system_time 102.60 -16.9% 85.26 aim7.time.user_time 715299 -32.7% 481312 aim7.time.voluntary_context_switches 31.39 +4.6% 32.84 boot-time.boot 24.75 +5.8% 26.17 boot-time.dhcp 1073 +3.8% 1114 boot-time.idle 23.78 ± 3% -19.7 4.03 ± 2% mpstat.cpu.all.idle% 0.03 ± 40% -0.0 0.00 ± 36% mpstat.cpu.all.iowait% 72.86 +22.5 95.34 mpstat.cpu.all.sys% 3.31 -2.7 0.62 mpstat.cpu.all.usr% 37946520 ± 4% +15.8% 43936831 numa-numastat.node0.local_node 37954399 ± 4% +15.8% 43943353 numa-numastat.node0.numa_hit 39497938 ± 3% -13.6% 34121982 numa-numastat.node1.local_node 39503258 ± 3% -13.6% 34128579 numa-numastat.node1.numa_hit 25.67 ± 5% -82.4% 4.53 ± 2% iostat.cpu.idle 71.06 +33.5% 94.85 iostat.cpu.system 3.25 ± 2% -80.9% 0.62 iostat.cpu.user 71.45 ± 13% -71.0% 20.71 ± 8% iostat.md0.w/s 2598 ± 35% -84.7% 397.41 ± 21% iostat.md0.wkB/s 52331183 ± 8% -88.0% 6278911 ± 8% cpuidle.C1.time 469089 ± 6% -85.8% 66489 ± 11% cpuidle.C1.usage 82837567 ± 43% -92.6% 6161783 ± 26% cpuidle.C1E.time 590943 ± 43% -92.7% 43113 ± 29% cpuidle.C1E.usage 5.515e+08 ± 14% -24.1% 4.185e+08 cpuidle.C6.time 15970 ± 4% -54.4% 7275 ± 10% cpuidle.POLL.time 25.50 ± 5% -84.3% 4.00 vmstat.cpu.id 70.50 ± 2% +33.3% 94.00 vmstat.cpu.sy 2597 ± 35% -84.7% 397.50 ± 21% vmstat.io.bo 30.75 +64.2% 50.50 vmstat.procs.r 18635 -76.3% 4421 vmstat.system.cs 82704 -1.5% 81496 vmstat.system.in 1160 +11.5% 1294 meminfo.Active(file) 79489 ± 3% +124.5% 178419 meminfo.AnonHugePages 5776899 ± 14% +21.9% 7039627 meminfo.DirectMap2M 206267 ± 8% +22.6% 252858 ± 14% meminfo.DirectMap4k 16915 ± 6% +15.8% 19586 meminfo.Dirty 64.50 ±135% +1520.9% 1045 ± 66% meminfo.Mlocked 37100 ± 2% +25.7% 46652 ± 4% meminfo.Shmem 34867 ± 4% -79.0% 7314 meminfo.max_used_kB 158732 ± 12% +29.9% 206208 ± 4% numa-meminfo.node0.Active 158381 ± 12% +30.0% 205908 ± 4% numa-meminfo.node0.Active(anon) 47728 ± 57% +141.7% 115362 ± 14% numa-meminfo.node0.AnonHugePages 153983 ± 13% +25.7% 193516 ± 10% numa-meminfo.node0.AnonPages 8151 ± 7% +21.4% 9894 numa-meminfo.node0.Dirty 8140 ± 5% +21.8% 9912 numa-meminfo.node0.Inactive(file) 32023 ± 83% +97.1% 63131 ± 25% numa-meminfo.node1.AnonHugePages 8247 ± 5% +16.4% 9602 numa-meminfo.node1.Dirty 35.00 ±146% +1547.1% 576.50 ± 74% numa-meminfo.node1.Mlocked 39629 ± 12% +29.9% 51479 ± 4% numa-vmstat.node0.nr_active_anon 38530 ± 13% +25.6% 48375 ± 10% numa-vmstat.node0.nr_anon_pages 15978818 ± 6% +33.2% 21290840 numa-vmstat.node0.nr_dirtied 1995 ± 2% +25.1% 2495 numa-vmstat.node0.nr_dirty 2032 +23.1% 2502 numa-vmstat.node0.nr_inactive_file 6.50 ±119% +1700.0% 117.00 ± 56% numa-vmstat.node0.nr_mlock 39629 ± 12% +29.9% 51479 ± 4% numa-vmstat.node0.nr_zone_active_anon 2030 +23.2% 2501 numa-vmstat.node0.nr_zone_inactive_file 1755 ± 4% +35.2% 2374 numa-vmstat.node0.nr_zone_write_pending 16510488 ± 6% +33.3% 22001420 numa-vmstat.node0.numa_hit 16502752 ± 6% +32.6% 21879456 numa-vmstat.node0.numa_local 7743 ± 40% +1475.2% 121965 ± 35% numa-vmstat.node0.numa_other 2061 ± 3% +18.3% 2439 numa-vmstat.node1.nr_dirty 7.75 ±144% +1758.1% 144.00 ± 74% numa-vmstat.node1.nr_mlock 1860 ± 3% +23.5% 2297 numa-vmstat.node1.nr_zone_write_pending 196119 -58.3% 81767 ± 52% numa-vmstat.node1.numa_other 2223 +37.3% 3051 turbostat.Avg_MHz 76.70 +19.4 96.06 turbostat.Busy% 464516 ± 6% -86.6% 62290 ± 10% turbostat.C1 1.61 ± 7% -1.6 0.04 turbostat.C1% 590696 ± 43% -92.8% 42693 ± 29% turbostat.C1E 2.55 ± 42% -2.5 0.04 ± 25% turbostat.C1E% 16.96 ± 12% -14.2 2.75 turbostat.C6% 12.86 ± 3% -84.1% 2.04 ± 3% turbostat.CPU%c1 9.76 ± 17% -84.9% 1.48 ± 4% turbostat.CPU%c6 119.72 +31.4% 157.31 turbostat.CorWatt 6809310 +355.8% 31038009 turbostat.IRQ 6.33 ± 17% -82.5% 1.11 ± 2% turbostat.Pkg%pc2 1.33 ± 47% -86.8% 0.17 ± 2% turbostat.Pkg%pc6 147.27 +27.0% 186.99 turbostat.PkgWatt 37.69 +28.6% 48.47 turbostat.RAMWatt 6460 +191.0% 18800 turbostat.SMI 89233 +7.5% 95956 proc-vmstat.nr_active_anon 287.25 +12.4% 323.00 proc-vmstat.nr_active_file 84940 +5.2% 89315 proc-vmstat.nr_anon_pages 4106 ± 5% +18.3% 4858 proc-vmstat.nr_dirty 327571 +1.0% 330803 proc-vmstat.nr_file_pages 5077 -1.9% 4979 proc-vmstat.nr_inactive_anon 4144 ± 5% +17.0% 4850 proc-vmstat.nr_inactive_file 53995 +3.3% 55798 proc-vmstat.nr_kernel_stack 6170 -2.4% 6019 proc-vmstat.nr_mapped 16.00 ±136% +1531.2% 261.00 ± 66% proc-vmstat.nr_mlock 9279 ± 2% +25.7% 11667 ± 4% proc-vmstat.nr_shmem 21055 +1.8% 21423 proc-vmstat.nr_slab_reclaimable 37405 +2.2% 38234 proc-vmstat.nr_slab_unreclaimable 89233 +7.5% 95956 proc-vmstat.nr_zone_active_anon 287.25 +12.4% 323.00 proc-vmstat.nr_zone_active_file 5077 -1.9% 4979 proc-vmstat.nr_zone_inactive_anon 4144 ± 5% +17.0% 4850 proc-vmstat.nr_zone_inactive_file 3554 ± 4% +29.3% 4594 proc-vmstat.nr_zone_write_pending 719.75 ±149% +8190.4% 59670 ± 4% proc-vmstat.numa_hint_faults 615.75 ±172% +5185.6% 32546 ± 9% proc-vmstat.numa_hint_faults_local 4064 ±116% +652.2% 30570 ± 12% proc-vmstat.numa_pages_migrated 15803 ± 96% +462.5% 88891 ± 4% proc-vmstat.numa_pte_updates 4867 ± 6% +15.7% 5633 ± 9% proc-vmstat.pgactivate 383704 ± 2% +202.9% 1162233 proc-vmstat.pgfault 4064 ±116% +652.2% 30570 ± 12% proc-vmstat.pgmigrate_success 1648 ± 2% +4.7% 1725 proc-vmstat.unevictable_pgs_culled 2583 ± 2% -30.4% 1798 slabinfo.dmaengine-unmap-16.active_objs 2586 ± 2% -30.5% 1798 slabinfo.dmaengine-unmap-16.num_objs 2018 ± 3% +17.4% 2370 slabinfo.ebitmap_node.active_objs 2018 ± 3% +17.4% 2370 slabinfo.ebitmap_node.num_objs 2435 +67.7% 4084 ± 2% slabinfo.kmalloc-128.active_objs 2435 +67.7% 4084 ± 2% slabinfo.kmalloc-128.num_objs 4185 ± 3% -12.1% 3680 slabinfo.kmalloc-192.active_objs 4191 ± 3% -11.5% 3711 ± 2% slabinfo.kmalloc-192.num_objs 5502 +15.7% 6368 slabinfo.kmalloc-512.active_objs 7072 ± 2% +15.4% 8164 slabinfo.kmalloc-96.active_objs 7203 +13.9% 8205 slabinfo.kmalloc-96.num_objs 12686 ± 7% +31.9% 16736 ± 9% slabinfo.lsm_file_cache.active_objs 12686 ± 7% +31.9% 16736 ± 9% slabinfo.lsm_file_cache.num_objs 2524 +13.3% 2860 slabinfo.names_cache.active_objs 2574 +14.0% 2933 slabinfo.names_cache.num_objs 118.75 ± 30% +134.1% 278.00 ± 8% slabinfo.nfs_commit_data.active_objs 118.75 ± 30% +134.1% 278.00 ± 8% slabinfo.nfs_commit_data.num_objs 5332 ± 3% -26.0% 3945 ± 5% slabinfo.pool_workqueue.active_objs 5347 ± 2% -26.2% 3946 ± 5% slabinfo.pool_workqueue.num_objs 1244 +12.3% 1396 slabinfo.xfs_btree_cur.active_objs 1244 +12.3% 1396 slabinfo.xfs_btree_cur.num_objs 1039 +13.1% 1176 slabinfo.xfs_buf_item.active_objs 1039 +13.1% 1176 slabinfo.xfs_buf_item.num_objs 1140 +13.0% 1289 slabinfo.xfs_da_state.active_objs 1140 +13.0% 1289 slabinfo.xfs_da_state.num_objs 1144 ± 3% +18.4% 1355 slabinfo.xfs_efd_item.active_objs 1144 ± 3% +18.4% 1355 slabinfo.xfs_efd_item.num_objs 2140 ± 2% -36.6% 1357 slabinfo.xfs_inode.active_objs 2223 -39.0% 1357 slabinfo.xfs_inode.num_objs 24.48 -19.9 4.58 ± 4% perf-profile.calltrace.cycles-pp.write 21.42 -17.4 4.04 ± 4% perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.write 21.28 -17.3 4.02 ± 4% perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 20.66 -16.7 3.93 ± 4% perf-profile.calltrace.cycles-pp.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 20.19 -16.3 3.84 ± 4% perf-profile.calltrace.cycles-pp.vfs_write.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe.write 18.01 -14.5 3.50 ± 3% perf-profile.calltrace.cycles-pp.new_sync_write.vfs_write.ksys_write.do_syscall_64.entry_SYSCALL_64_after_hwframe 17.11 -13.8 3.36 ± 4% perf-profile.calltrace.cycles-pp.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write.do_syscall_64 13.64 -11.1 2.55 ± 3% perf-profile.calltrace.cycles-pp.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write 13.56 -11.0 2.54 ± 3% perf-profile.calltrace.cycles-pp.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write.vfs_write 11.81 -11.0 0.82 ± 7% perf-profile.calltrace.cycles-pp.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 11.72 -10.9 0.79 ± 8% perf-profile.calltrace.cycles-pp.atime_needs_update.touch_atime.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 10.27 -8.4 1.91 ± 4% perf-profile.calltrace.cycles-pp.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write 8.05 -7.5 0.58 ± 5% perf-profile.calltrace.cycles-pp.xfs_ilock.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read 7.99 -7.4 0.58 ± 5% perf-profile.calltrace.cycles-pp.down_read.xfs_ilock.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 7.27 ± 4% -7.3 0.00 perf-profile.calltrace.cycles-pp.security_file_permission.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe 6.16 ± 2% -5.9 0.27 ±100% perf-profile.calltrace.cycles-pp.up_read.xfs_iunlock.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 6.21 ± 2% -5.7 0.52 ± 3% perf-profile.calltrace.cycles-pp.xfs_iunlock.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read 5.04 ± 4% -5.0 0.00 perf-profile.calltrace.cycles-pp.selinux_file_permission.security_file_permission.vfs_read.ksys_read.do_syscall_64 5.42 -4.4 1.01 ± 4% perf-profile.calltrace.cycles-pp.iomap_write_begin.iomap_write_actor.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write 4.12 -3.3 0.78 ± 7% perf-profile.calltrace.cycles-pp.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor.iomap_apply.iomap_file_buffered_write 3.95 -3.2 0.73 ± 6% perf-profile.calltrace.cycles-pp.pagecache_get_page.grab_cache_page_write_begin.iomap_write_begin.iomap_write_actor.iomap_apply 2.40 ± 3% -1.9 0.51 perf-profile.calltrace.cycles-pp.xfs_file_iomap_begin.iomap_apply.iomap_file_buffered_write.xfs_file_buffered_aio_write.new_sync_write 2.39 -1.8 0.58 ± 6% perf-profile.calltrace.cycles-pp.xfs_file_aio_write_checks.xfs_file_buffered_aio_write.new_sync_write.vfs_write.ksys_write 1.64 -0.4 1.25 ± 2% perf-profile.calltrace.cycles-pp.copy_page_to_iter.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 0.56 ± 7% +1.5 2.02 perf-profile.calltrace.cycles-pp.xas_start.xas_load.find_get_entry.pagecache_get_page.generic_file_read_iter 0.00 +1.8 1.77 ± 4% perf-profile.calltrace.cycles-pp.___might_sleep.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 0.75 ± 6% +3.4 4.12 perf-profile.calltrace.cycles-pp.xas_load.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read 0.00 +6.6 6.58 ± 4% perf-profile.calltrace.cycles-pp.mark_page_accessed.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 66.40 +28.0 94.41 perf-profile.calltrace.cycles-pp.read 62.72 +31.1 93.86 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe.read 62.59 +31.2 93.83 perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 61.99 +31.7 93.72 perf-profile.calltrace.cycles-pp.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 61.50 +32.1 93.65 perf-profile.calltrace.cycles-pp.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe.read 49.59 +43.5 93.05 perf-profile.calltrace.cycles-pp.new_sync_read.vfs_read.ksys_read.do_syscall_64.entry_SYSCALL_64_after_hwframe 2.29 ± 3% +47.1 49.36 perf-profile.calltrace.cycles-pp.find_get_entry.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter 2.34 ± 3% +47.8 50.17 perf-profile.calltrace.cycles-pp.pagecache_get_page.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read 41.75 +51.0 92.78 perf-profile.calltrace.cycles-pp.xfs_file_read_iter.new_sync_read.vfs_read.ksys_read.do_syscall_64 37.36 +55.3 92.64 perf-profile.calltrace.cycles-pp.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read.ksys_read 23.02 +68.2 91.25 perf-profile.calltrace.cycles-pp.generic_file_read_iter.xfs_file_buffered_aio_read.xfs_file_read_iter.new_sync_read.vfs_read 16.69 ± 4% -37.3% 10.47 perf-stat.i.MPKI 4.871e+09 +42.2% 6.925e+09 perf-stat.i.branch-instructions 2.68 ± 8% -2.0 0.66 ± 4% perf-stat.i.branch-miss-rate% 66135811 ± 2% -55.2% 29604797 perf-stat.i.branch-misses 12.56 ± 3% +19.2 31.78 perf-stat.i.cache-miss-rate% 28607414 +253.7% 1.012e+08 perf-stat.i.cache-misses 2.693e+08 +17.3% 3.16e+08 perf-stat.i.cache-references 19130 -76.9% 4419 perf-stat.i.context-switches 4.00 -6.7% 3.73 perf-stat.i.cpi 8.942e+10 +36.0% 1.216e+11 perf-stat.i.cpu-cycles 2280 -66.5% 764.28 perf-stat.i.cpu-migrations 2819 ± 2% -57.8% 1189 ± 2% perf-stat.i.cycles-between-cache-misses 1.91 ± 6% -0.6 1.26 ± 12% perf-stat.i.dTLB-load-miss-rate% 1.636e+08 ± 7% -28.5% 1.17e+08 ± 14% perf-stat.i.dTLB-load-misses 7.678e+09 +17.2% 9.002e+09 perf-stat.i.dTLB-loads 5.022e+09 +2.3% 5.138e+09 perf-stat.i.dTLB-stores 8198957 ± 4% -75.3% 2023647 ± 2% perf-stat.i.iTLB-load-misses 1570759 ± 18% -75.7% 381261 ± 48% perf-stat.i.iTLB-loads 2.463e+10 +33.6% 3.29e+10 perf-stat.i.instructions 2775 ± 3% +479.2% 16074 perf-stat.i.instructions-per-iTLB-miss 4535 -34.2% 2986 perf-stat.i.minor-faults 46.43 +0.7 47.17 perf-stat.i.node-load-miss-rate% 15958314 +262.7% 57878361 ± 3% perf-stat.i.node-load-misses 18031706 +255.5% 64100733 ± 2% perf-stat.i.node-loads 7699378 +268.1% 28341867 perf-stat.i.node-store-misses 9555974 +292.0% 37461477 perf-stat.i.node-stores 4535 -34.2% 2986 perf-stat.i.page-faults 10.93 -12.2% 9.60 perf-stat.overall.MPKI 1.36 -0.9 0.43 perf-stat.overall.branch-miss-rate% 10.62 +21.4 32.02 perf-stat.overall.cache-miss-rate% 3.63 +1.9% 3.70 perf-stat.overall.cpi 3125 -61.5% 1202 perf-stat.overall.cycles-between-cache-misses 2.09 ± 6% -0.8 1.28 ± 12% perf-stat.overall.dTLB-load-miss-rate% 3011 ± 4% +440.1% 16262 perf-stat.overall.instructions-per-iTLB-miss 44.62 -1.5 43.07 perf-stat.overall.node-store-miss-rate% 4.808e+09 +43.6% 6.906e+09 perf-stat.ps.branch-instructions 65286911 ± 2% -54.8% 29529411 perf-stat.ps.branch-misses 28238780 +257.3% 1.009e+08 perf-stat.ps.cache-misses 2.658e+08 +18.5% 3.151e+08 perf-stat.ps.cache-references 18882 -76.7% 4407 perf-stat.ps.context-switches 8.825e+10 +37.5% 1.213e+11 perf-stat.ps.cpu-cycles 2250 -66.1% 762.20 perf-stat.ps.cpu-migrations 1.615e+08 ± 7% -27.7% 1.167e+08 ± 14% perf-stat.ps.dTLB-load-misses 7.579e+09 +18.5% 8.977e+09 perf-stat.ps.dTLB-loads 4.957e+09 +3.4% 5.124e+09 perf-stat.ps.dTLB-stores 8092496 ± 4% -75.1% 2018134 ± 2% perf-stat.ps.iTLB-load-misses 1550345 ± 18% -75.5% 380213 ± 48% perf-stat.ps.iTLB-loads 2.431e+10 +34.9% 3.281e+10 perf-stat.ps.instructions 4485 -33.6% 2979 perf-stat.ps.minor-faults 78985 +1.0% 79787 perf-stat.ps.msec 15750551 +266.5% 57718276 ± 3% perf-stat.ps.node-load-misses 17797012 +259.2% 63923411 ± 2% perf-stat.ps.node-loads 7599430 +271.9% 28263476 perf-stat.ps.node-store-misses 9432838 +296.0% 37357987 perf-stat.ps.node-stores 4485 -33.6% 2979 perf-stat.ps.page-faults 1.944e+12 +539.2% 1.243e+13 perf-stat.total.instructions 11300 ± 4% +37.0% 15483 softirqs.CPU0.RCU 38205 ± 2% +340.7% 168362 softirqs.CPU0.TIMER 10724 ± 6% +63.0% 17483 ± 17% softirqs.CPU1.RCU 33429 ± 3% +448.7% 183422 ± 16% softirqs.CPU1.TIMER 11440 ± 5% +68.7% 19299 ± 7% softirqs.CPU10.RCU 35285 ± 3% +386.2% 171569 ± 5% softirqs.CPU10.TIMER 10439 ± 5% +25.1% 13064 softirqs.CPU11.RCU 34696 ± 3% +352.7% 157067 ± 4% softirqs.CPU11.TIMER 39317 ± 6% +317.6% 164203 ± 2% softirqs.CPU12.TIMER 11453 ± 11% +13.8% 13037 ± 5% softirqs.CPU13.RCU 35175 ± 4% +342.5% 155666 ± 5% softirqs.CPU13.TIMER 10594 ± 3% +38.0% 14624 softirqs.CPU14.RCU 8846 ± 2% +8.5% 9602 ± 4% softirqs.CPU14.SCHED 36407 +347.0% 162753 softirqs.CPU14.TIMER 11327 ± 11% +17.1% 13267 softirqs.CPU15.RCU 35261 ± 4% +356.7% 161037 ± 4% softirqs.CPU15.TIMER 37699 ± 6% +338.9% 165465 ± 2% softirqs.CPU16.TIMER 10542 ± 3% +33.3% 14055 ± 7% softirqs.CPU17.RCU 35568 ± 4% +352.3% 160870 ± 3% softirqs.CPU17.TIMER 10503 ± 9% +45.2% 15246 ± 10% softirqs.CPU18.RCU 8824 ± 3% +9.3% 9641 ± 4% softirqs.CPU18.SCHED 36329 +345.0% 161670 softirqs.CPU18.TIMER 10560 ± 9% +20.9% 12770 ± 2% softirqs.CPU19.RCU 35217 ± 4% +348.3% 157892 ± 4% softirqs.CPU19.TIMER 11935 ± 6% +25.0% 14913 ± 2% softirqs.CPU2.RCU 40085 ± 21% +308.5% 163727 softirqs.CPU2.TIMER 10580 ± 6% +33.3% 14108 ± 2% softirqs.CPU20.RCU 35607 ± 3% +367.2% 166363 softirqs.CPU20.TIMER 10779 ± 5% +18.8% 12808 softirqs.CPU21.RCU 34607 +390.2% 169655 ± 8% softirqs.CPU21.TIMER 10214 ± 3% +42.6% 14566 softirqs.CPU22.RCU 35941 +362.4% 166191 softirqs.CPU22.TIMER 10428 ± 4% +22.4% 12766 ± 2% softirqs.CPU23.RCU 36565 ± 6% +337.8% 160071 ± 4% softirqs.CPU23.TIMER 11727 ± 10% +31.8% 15459 ± 7% softirqs.CPU24.RCU 37658 ± 8% +342.1% 166490 softirqs.CPU24.TIMER 10509 ± 3% +23.4% 12967 ± 3% softirqs.CPU25.RCU 35179 ± 2% +359.4% 161626 ± 4% softirqs.CPU25.TIMER 10700 ± 2% +35.0% 14446 ± 3% softirqs.CPU26.RCU 36295 ± 3% +353.5% 164615 softirqs.CPU26.TIMER 11108 ± 5% +17.9% 13096 softirqs.CPU27.RCU 36245 ± 6% +344.5% 161123 ± 3% softirqs.CPU27.TIMER 10762 ± 5% +37.0% 14746 ± 2% softirqs.CPU28.RCU 35529 ± 2% +359.1% 163130 softirqs.CPU28.TIMER 34944 ± 3% +348.8% 156849 ± 4% softirqs.CPU29.TIMER 10712 ± 7% +27.0% 13602 softirqs.CPU3.RCU 38235 ± 15% +318.8% 160146 ± 4% softirqs.CPU3.TIMER 11682 ± 9% +48.6% 17357 ± 5% softirqs.CPU30.RCU 39787 ± 26% +358.7% 182513 ± 11% softirqs.CPU30.TIMER 11089 ± 13% +23.1% 13652 ± 6% softirqs.CPU31.RCU 35040 ± 5% +346.6% 156483 ± 5% softirqs.CPU31.TIMER 37864 ± 5% +333.5% 164148 ± 2% softirqs.CPU32.TIMER 34838 ± 4% +346.1% 155416 ± 5% softirqs.CPU33.TIMER 9059 ± 11% +28.6% 11654 ± 5% softirqs.CPU34.RCU 36135 +352.8% 163637 softirqs.CPU34.TIMER 9929 ± 13% +20.5% 11964 ± 6% softirqs.CPU35.RCU 35253 ± 3% +355.4% 160552 ± 4% softirqs.CPU35.TIMER 9812 ± 7% +28.1% 12569 ± 10% softirqs.CPU36.RCU 36233 +356.0% 165213 ± 2% softirqs.CPU36.TIMER 8617 ± 6% +19.9% 10331 softirqs.CPU37.RCU 34947 ± 3% +360.5% 160950 ± 2% softirqs.CPU37.TIMER 9614 ± 14% +33.1% 12801 ± 8% softirqs.CPU38.RCU 36368 +344.5% 161670 softirqs.CPU38.TIMER 35076 ± 4% +349.6% 157695 ± 4% softirqs.CPU39.TIMER 11551 ± 11% +28.1% 14798 softirqs.CPU4.RCU 36610 +355.5% 166772 softirqs.CPU4.TIMER 35479 ± 2% +355.4% 161573 ± 4% softirqs.CPU5.TIMER 10648 ± 2% +39.9% 14894 softirqs.CPU6.RCU 36168 ± 2% +354.4% 164361 softirqs.CPU6.TIMER 12361 ± 8% +18.1% 14604 ± 5% softirqs.CPU7.RCU 41756 ± 27% +283.5% 160130 ± 3% softirqs.CPU7.TIMER 11070 ± 8% +42.1% 15727 ± 4% softirqs.CPU8.RCU 35520 ± 2% +359.7% 163300 softirqs.CPU8.TIMER 10999 ± 8% +19.7% 13168 softirqs.CPU9.RCU 35178 ± 3% +346.3% 157017 ± 5% softirqs.CPU9.TIMER 431390 ± 2% +28.1% 552492 softirqs.RCU 1451755 ± 2% +349.9% 6531407 ± 2% softirqs.TIMER 17335 ± 8% +50.0% 25998 ± 2% sched_debug.cfs_rq:/.load.avg 49802 ± 5% +31.5% 65479 ± 9% sched_debug.cfs_rq:/.load.max 109.88 ± 25% -50.3% 54.58 ± 11% sched_debug.cfs_rq:/.load_avg.avg 787480 +761.6% 6784621 sched_debug.cfs_rq:/.min_vruntime.avg 880219 ± 4% +703.3% 7070715 sched_debug.cfs_rq:/.min_vruntime.max 770885 +747.1% 6530040 sched_debug.cfs_rq:/.min_vruntime.min 18301 ± 28% +830.8% 170356 ± 10% sched_debug.cfs_rq:/.min_vruntime.stddev 0.58 ± 8% +54.4% 0.89 sched_debug.cfs_rq:/.nr_running.avg 0.37 ± 7% -74.9% 0.09 ± 38% sched_debug.cfs_rq:/.nr_running.stddev 41.05 ± 33% -82.2% 7.29 sched_debug.cfs_rq:/.removed.load_avg.avg 510.88 -71.4% 146.29 sched_debug.cfs_rq:/.removed.load_avg.max 135.76 ± 15% -76.6% 31.78 sched_debug.cfs_rq:/.removed.load_avg.stddev 1893 ± 33% -82.2% 337.03 sched_debug.cfs_rq:/.removed.runnable_sum.avg 23609 -71.3% 6787 sched_debug.cfs_rq:/.removed.runnable_sum.max 6261 ± 15% -76.5% 1469 sched_debug.cfs_rq:/.removed.runnable_sum.stddev 10.72 ± 57% -76.9% 2.47 ± 34% sched_debug.cfs_rq:/.removed.util_avg.avg 174.75 ± 33% -68.1% 55.71 ± 32% sched_debug.cfs_rq:/.removed.util_avg.max 38.33 ± 43% -71.6% 10.87 ± 34% sched_debug.cfs_rq:/.removed.util_avg.stddev 13.12 ± 11% +59.8% 20.96 sched_debug.cfs_rq:/.runnable_load_avg.avg 39.25 ± 7% +56.1% 61.29 ± 3% sched_debug.cfs_rq:/.runnable_load_avg.max 9.49 ± 6% +22.5% 11.63 ± 3% sched_debug.cfs_rq:/.runnable_load_avg.stddev 15014 ± 7% +39.4% 20929 sched_debug.cfs_rq:/.runnable_weight.avg 36981 ± 7% +32.4% 48981 sched_debug.cfs_rq:/.runnable_weight.max -655.34 -22775.6% 148603 ± 3% sched_debug.cfs_rq:/.spread0.avg 92077 ± 49% +372.2% 434756 ± 7% sched_debug.cfs_rq:/.spread0.max -17235 +513.2% -105683 sched_debug.cfs_rq:/.spread0.min 18312 ± 28% +830.1% 170323 ± 10% sched_debug.cfs_rq:/.spread0.stddev 773.86 ± 4% +23.2% 953.22 sched_debug.cfs_rq:/.util_avg.avg 1596 ± 9% +40.5% 2243 ± 7% sched_debug.cfs_rq:/.util_avg.max 309.13 ± 11% +30.8% 404.46 ± 10% sched_debug.cfs_rq:/.util_avg.stddev 168.92 ± 16% +251.7% 594.11 ± 4% sched_debug.cfs_rq:/.util_est_enqueued.avg 712.88 ± 22% +143.8% 1738 ± 5% sched_debug.cfs_rq:/.util_est_enqueued.max 165.72 ± 17% +108.2% 345.00 sched_debug.cfs_rq:/.util_est_enqueued.stddev 415111 ± 5% +58.1% 656270 sched_debug.cpu.avg_idle.avg 62646 ± 20% +415.9% 323170 ± 13% sched_debug.cpu.avg_idle.min 225351 ± 8% -21.7% 176447 sched_debug.cpu.avg_idle.stddev 69939 +213.6% 219304 sched_debug.cpu.clock.avg 69948 +213.5% 219322 sched_debug.cpu.clock.max 69929 +213.6% 219284 sched_debug.cpu.clock.min 5.54 ± 15% +100.7% 11.12 sched_debug.cpu.clock.stddev 69939 +213.6% 219304 sched_debug.cpu.clock_task.avg 69948 +213.5% 219322 sched_debug.cpu.clock_task.max 69929 +213.6% 219284 sched_debug.cpu.clock_task.min 5.54 ± 15% +100.7% 11.12 sched_debug.cpu.clock_task.stddev 13.70 ± 13% +67.5% 22.95 ± 6% sched_debug.cpu.cpu_load[0].avg 40.25 ± 12% +246.2% 139.36 ± 57% sched_debug.cpu.cpu_load[0].max 9.51 ± 5% +144.4% 23.23 ± 50% sched_debug.cpu.cpu_load[0].stddev 14.31 ± 11% +61.5% 23.10 ± 5% sched_debug.cpu.cpu_load[1].avg 33.38 ± 7% +192.8% 97.71 ± 41% sched_debug.cpu.cpu_load[1].max 1.12 ±148% +534.9% 7.14 sched_debug.cpu.cpu_load[1].min 7.73 ± 10% +123.5% 17.28 ± 36% sched_debug.cpu.cpu_load[1].stddev 15.17 ± 9% +51.7% 23.01 ± 2% sched_debug.cpu.cpu_load[2].avg 37.62 ± 16% +106.7% 77.79 ± 21% sched_debug.cpu.cpu_load[2].max 1.88 ±103% +300.0% 7.50 ± 2% sched_debug.cpu.cpu_load[2].min 7.43 ± 11% +91.4% 14.21 ± 21% sched_debug.cpu.cpu_load[2].stddev 16.76 ± 7% +37.2% 22.98 sched_debug.cpu.cpu_load[3].avg 3.38 ± 36% +139.2% 8.07 sched_debug.cpu.cpu_load[3].min 11.42 ± 4% +8.8% 12.42 ± 6% sched_debug.cpu.cpu_load[3].stddev 19.03 ± 3% +21.8% 23.19 sched_debug.cpu.cpu_load[4].avg 173.25 ± 3% -48.9% 88.50 ± 3% sched_debug.cpu.cpu_load[4].max 4.62 ± 4% +85.3% 8.57 sched_debug.cpu.cpu_load[4].min 26.77 ± 2% -44.3% 14.92 ± 3% sched_debug.cpu.cpu_load[4].stddev 1725 ± 13% +62.4% 2803 ± 5% sched_debug.cpu.curr->pid.avg 3860 ± 9% +98.5% 7662 ± 2% sched_debug.cpu.curr->pid.max 17235 ± 9% +50.1% 25869 sched_debug.cpu.load.avg 49790 ± 5% +31.5% 65479 ± 9% sched_debug.cpu.load.max 0.00 ± 6% +65.8% 0.00 ± 29% sched_debug.cpu.next_balance.stddev 40051 +376.3% 190749 sched_debug.cpu.nr_load_updates.avg 48118 ± 4% +315.5% 199922 sched_debug.cpu.nr_load_updates.max 37637 +401.8% 188874 sched_debug.cpu.nr_load_updates.min 0.61 ± 11% +83.4% 1.12 ± 7% sched_debug.cpu.nr_running.avg 1.62 ± 13% +62.6% 2.64 ± 8% sched_debug.cpu.nr_running.max 0.43 ± 8% +17.0% 0.51 ± 8% sched_debug.cpu.nr_running.stddev 15323 +38.3% 21185 sched_debug.cpu.nr_switches.avg 23666 ± 3% +33.5% 31603 ± 2% sched_debug.cpu.nr_switches.max 13256 +27.2% 16862 sched_debug.cpu.nr_switches.min 2125 ± 4% +45.4% 3091 ± 4% sched_debug.cpu.nr_switches.stddev 36.53 +57.0% 57.34 sched_debug.cpu.nr_uninterruptible.avg 121.62 ± 10% +53.4% 186.57 ± 6% sched_debug.cpu.nr_uninterruptible.max 35.08 ± 12% +51.7% 53.23 ± 7% sched_debug.cpu.nr_uninterruptible.stddev 69929 +213.6% 219281 sched_debug.cpu_clk 66357 +224.9% 215625 sched_debug.ktime 70373 +212.3% 219744 sched_debug.sched_clk 187.50 ± 32% +270.7% 695.00 interrupts.37:IR-PCI-MSI.524289-edge.eth0-TxRx-0 87.75 ± 49% +149.6% 219.00 interrupts.39:IR-PCI-MSI.524291-edge.eth0-TxRx-2 133.00 ± 60% +129.3% 305.00 ± 4% interrupts.40:IR-PCI-MSI.524292-edge.eth0-TxRx-3 157.75 ± 95% +204.0% 479.50 ± 32% interrupts.41:IR-PCI-MSI.524293-edge.eth0-TxRx-4 57.75 ± 6% +409.1% 294.00 ± 25% interrupts.42:IR-PCI-MSI.524294-edge.eth0-TxRx-5 93.50 ± 75% +749.7% 794.50 ± 31% interrupts.43:IR-PCI-MSI.524295-edge.eth0-TxRx-6 55.75 ± 12% +979.8% 602.00 interrupts.44:IR-PCI-MSI.524296-edge.eth0-TxRx-7 39.75 ± 2% +366.7% 185.50 interrupts.94:IR-PCI-MSI.512000-edge.ahci[0000:00:1f.2] 41912 ± 9% +213.8% 131529 interrupts.CAL:Function_call_interrupts 1078 ± 10% +217.8% 3426 ± 6% interrupts.CPU0.CAL:Function_call_interrupts 160883 +371.4% 758361 interrupts.CPU0.LOC:Local_timer_interrupts 3951 ± 70% +128.9% 9046 interrupts.CPU0.NMI:Non-maskable_interrupts 3951 ± 70% +128.9% 9046 interrupts.CPU0.PMI:Performance_monitoring_interrupts 2756 ± 14% +212.4% 8612 ± 3% interrupts.CPU0.RES:Rescheduling_interrupts 1052 ± 7% +209.7% 3260 ± 7% interrupts.CPU1.CAL:Function_call_interrupts 160927 +371.3% 758448 interrupts.CPU1.LOC:Local_timer_interrupts 2268 ± 16% +241.3% 7743 ± 9% interrupts.CPU1.RES:Rescheduling_interrupts 949.25 ± 18% +238.6% 3214 interrupts.CPU10.CAL:Function_call_interrupts 160048 ± 2% +373.5% 757791 interrupts.CPU10.LOC:Local_timer_interrupts 2401 ± 26% +269.4% 8870 ± 6% interrupts.CPU10.RES:Rescheduling_interrupts 1078 ± 9% +208.4% 3325 ± 4% interrupts.CPU11.CAL:Function_call_interrupts 160525 +372.2% 757955 interrupts.CPU11.LOC:Local_timer_interrupts 2224 ± 5% +223.7% 7202 ± 6% interrupts.CPU11.RES:Rescheduling_interrupts 1084 ± 10% +186.2% 3103 interrupts.CPU12.CAL:Function_call_interrupts 160874 +371.2% 758018 interrupts.CPU12.LOC:Local_timer_interrupts 2084 ± 2% +290.9% 8147 ± 4% interrupts.CPU12.RES:Rescheduling_interrupts 1081 ± 11% +194.8% 3186 ± 10% interrupts.CPU13.CAL:Function_call_interrupts 160936 +371.0% 757976 interrupts.CPU13.LOC:Local_timer_interrupts 2226 ± 2% +191.5% 6490 interrupts.CPU13.RES:Rescheduling_interrupts 1091 ± 9% +223.0% 3526 ± 2% interrupts.CPU14.CAL:Function_call_interrupts 160591 +372.2% 758257 interrupts.CPU14.LOC:Local_timer_interrupts 2239 ± 11% +291.6% 8771 ± 11% interrupts.CPU14.RES:Rescheduling_interrupts 1079 ± 11% +208.8% 3331 ± 5% interrupts.CPU15.CAL:Function_call_interrupts 160602 +372.1% 758250 interrupts.CPU15.LOC:Local_timer_interrupts 2150 ± 3% +209.2% 6647 interrupts.CPU15.RES:Rescheduling_interrupts 1064 ± 12% +228.0% 3490 interrupts.CPU16.CAL:Function_call_interrupts 160603 +371.8% 757703 interrupts.CPU16.LOC:Local_timer_interrupts 2102 ± 2% +288.3% 8162 ± 3% interrupts.CPU16.RES:Rescheduling_interrupts 997.75 ± 9% +227.0% 3262 ± 7% interrupts.CPU17.CAL:Function_call_interrupts 160890 +371.2% 758088 interrupts.CPU17.LOC:Local_timer_interrupts 2114 ± 2% +216.2% 6683 interrupts.CPU17.RES:Rescheduling_interrupts 1042 ± 7% +187.8% 3001 ± 4% interrupts.CPU18.CAL:Function_call_interrupts 160581 +372.1% 758185 interrupts.CPU18.LOC:Local_timer_interrupts 2195 ± 9% +319.5% 9210 ± 7% interrupts.CPU18.RES:Rescheduling_interrupts 1033 ± 10% +215.9% 3263 ± 5% interrupts.CPU19.CAL:Function_call_interrupts 160518 +372.4% 758272 interrupts.CPU19.LOC:Local_timer_interrupts 2198 ± 4% +307.0% 8945 interrupts.CPU19.RES:Rescheduling_interrupts 55.75 ± 12% +979.8% 602.00 interrupts.CPU2.44:IR-PCI-MSI.524296-edge.eth0-TxRx-7 1077 ± 9% +208.1% 3319 ± 4% interrupts.CPU2.CAL:Function_call_interrupts 160815 +371.5% 758168 interrupts.CPU2.LOC:Local_timer_interrupts 2070 ± 4% +383.7% 10015 interrupts.CPU2.RES:Rescheduling_interrupts 1050 ± 6% +209.2% 3247 ± 7% interrupts.CPU20.CAL:Function_call_interrupts 160541 +372.1% 757904 interrupts.CPU20.LOC:Local_timer_interrupts 2020 ± 3% +301.7% 8117 ± 2% interrupts.CPU20.RES:Rescheduling_interrupts 1030 ± 10% +211.6% 3210 ± 3% interrupts.CPU21.CAL:Function_call_interrupts 160769 +371.6% 758128 interrupts.CPU21.LOC:Local_timer_interrupts 1957 ±173% +228.8% 6435 ± 44% interrupts.CPU21.NMI:Non-maskable_interrupts 1957 ±173% +228.8% 6435 ± 44% interrupts.CPU21.PMI:Performance_monitoring_interrupts 2120 ± 3% +205.5% 6477 interrupts.CPU21.RES:Rescheduling_interrupts 1026 ± 10% +211.6% 3198 ± 12% interrupts.CPU22.CAL:Function_call_interrupts 160736 +371.6% 757984 interrupts.CPU22.LOC:Local_timer_interrupts 2042 ± 2% +301.8% 8205 interrupts.CPU22.RES:Rescheduling_interrupts 1035 ± 8% +195.1% 3056 interrupts.CPU23.CAL:Function_call_interrupts 160511 +372.5% 758362 interrupts.CPU23.LOC:Local_timer_interrupts 2116 ± 2% +234.4% 7076 ± 5% interrupts.CPU23.RES:Rescheduling_interrupts 1062 ± 9% +201.8% 3205 ± 10% interrupts.CPU24.CAL:Function_call_interrupts 160679 +372.0% 758454 interrupts.CPU24.LOC:Local_timer_interrupts 2075 +288.5% 8063 interrupts.CPU24.RES:Rescheduling_interrupts 1038 ± 8% +243.2% 3563 interrupts.CPU25.CAL:Function_call_interrupts 160868 +371.3% 758094 interrupts.CPU25.LOC:Local_timer_interrupts 2108 +210.2% 6540 ± 3% interrupts.CPU25.RES:Rescheduling_interrupts 187.50 ± 32% +270.7% 695.00 interrupts.CPU26.37:IR-PCI-MSI.524289-edge.eth0-TxRx-0 1007 ± 7% +223.5% 3260 ± 3% interrupts.CPU26.CAL:Function_call_interrupts 160779 +371.6% 758284 interrupts.CPU26.LOC:Local_timer_interrupts 2098 ± 2% +291.7% 8219 interrupts.CPU26.RES:Rescheduling_interrupts 1048 ± 9% +193.2% 3073 interrupts.CPU27.CAL:Function_call_interrupts 160687 +371.9% 758313 interrupts.CPU27.LOC:Local_timer_interrupts 2109 ± 4% +245.1% 7278 ± 6% interrupts.CPU27.RES:Rescheduling_interrupts 1036 ± 12% +242.1% 3544 interrupts.CPU28.CAL:Function_call_interrupts 160492 +372.3% 757965 interrupts.CPU28.LOC:Local_timer_interrupts 991.00 ±172% +580.5% 6744 ± 30% interrupts.CPU28.NMI:Non-maskable_interrupts 991.00 ±172% +580.5% 6744 ± 30% interrupts.CPU28.PMI:Performance_monitoring_interrupts 2149 ± 6% +333.0% 9305 interrupts.CPU28.RES:Rescheduling_interrupts 998.00 ± 5% +224.9% 3243 ± 8% interrupts.CPU29.CAL:Function_call_interrupts 160614 +372.2% 758375 interrupts.CPU29.LOC:Local_timer_interrupts 1277 ±127% +260.2% 4601 interrupts.CPU29.NMI:Non-maskable_interrupts 1277 ±127% +260.2% 4601 interrupts.CPU29.PMI:Performance_monitoring_interrupts 2169 +212.4% 6776 interrupts.CPU29.RES:Rescheduling_interrupts 1084 ± 11% +224.5% 3519 interrupts.CPU3.CAL:Function_call_interrupts 160908 +371.1% 757989 interrupts.CPU3.LOC:Local_timer_interrupts 2284 ± 12% +192.3% 6675 interrupts.CPU3.RES:Rescheduling_interrupts 87.75 ± 49% +149.6% 219.00 interrupts.CPU30.39:IR-PCI-MSI.524291-edge.eth0-TxRx-2 1085 ± 11% +185.3% 3097 ± 15% interrupts.CPU30.CAL:Function_call_interrupts 160639 +372.1% 758299 interrupts.CPU30.LOC:Local_timer_interrupts 2114 ± 5% +285.7% 8157 ± 2% interrupts.CPU30.RES:Rescheduling_interrupts 1058 ± 9% +216.8% 3354 ± 6% interrupts.CPU31.CAL:Function_call_interrupts 160640 +371.9% 757999 interrupts.CPU31.LOC:Local_timer_interrupts 2115 ± 5% +234.4% 7073 ± 5% interrupts.CPU31.RES:Rescheduling_interrupts 133.00 ± 60% +129.3% 305.00 ± 4% interrupts.CPU32.40:IR-PCI-MSI.524292-edge.eth0-TxRx-3 1028 ± 9% +249.1% 3590 interrupts.CPU32.CAL:Function_call_interrupts 160441 +372.6% 758242 interrupts.CPU32.LOC:Local_timer_interrupts 1292 ±123% +600.6% 9056 interrupts.CPU32.NMI:Non-maskable_interrupts 1292 ±123% +600.6% 9056 interrupts.CPU32.PMI:Performance_monitoring_interrupts 2161 ± 3% +269.5% 7984 ± 2% interrupts.CPU32.RES:Rescheduling_interrupts 1052 ± 7% +197.5% 3129 ± 7% interrupts.CPU33.CAL:Function_call_interrupts 160555 +372.2% 758200 interrupts.CPU33.LOC:Local_timer_interrupts 2129 ± 2% +212.0% 6644 interrupts.CPU33.RES:Rescheduling_interrupts 157.75 ± 95% +204.0% 479.50 ± 32% interrupts.CPU34.41:IR-PCI-MSI.524293-edge.eth0-TxRx-4 1038 ± 11% +199.1% 3106 interrupts.CPU34.CAL:Function_call_interrupts 160579 +372.0% 757860 interrupts.CPU34.LOC:Local_timer_interrupts 2041 ± 3% +361.8% 9427 ± 9% interrupts.CPU34.RES:Rescheduling_interrupts 1013 ± 7% +232.2% 3366 ± 7% interrupts.CPU35.CAL:Function_call_interrupts 160263 +373.1% 758135 interrupts.CPU35.LOC:Local_timer_interrupts 2087 ± 3% +230.3% 6893 ± 6% interrupts.CPU35.RES:Rescheduling_interrupts 57.75 ± 6% +409.1% 294.00 ± 25% interrupts.CPU36.42:IR-PCI-MSI.524294-edge.eth0-TxRx-5 1043 ± 11% +193.5% 3062 ± 3% interrupts.CPU36.CAL:Function_call_interrupts 160457 +372.5% 758097 interrupts.CPU36.LOC:Local_timer_interrupts 2142 ± 2% +291.2% 8381 ± 4% interrupts.CPU36.RES:Rescheduling_interrupts 1042 ± 11% +240.9% 3554 interrupts.CPU37.CAL:Function_call_interrupts 159944 +374.0% 758180 interrupts.CPU37.LOC:Local_timer_interrupts 2029 ± 93% +234.1% 6781 ± 32% interrupts.CPU37.NMI:Non-maskable_interrupts 2029 ± 93% +234.1% 6781 ± 32% interrupts.CPU37.PMI:Performance_monitoring_interrupts 2109 ± 4% +215.2% 6647 ± 2% interrupts.CPU37.RES:Rescheduling_interrupts 93.50 ± 75% +749.7% 794.50 ± 31% interrupts.CPU38.43:IR-PCI-MSI.524295-edge.eth0-TxRx-6 1083 ± 12% +230.4% 3578 interrupts.CPU38.CAL:Function_call_interrupts 160648 +371.5% 757502 interrupts.CPU38.LOC:Local_timer_interrupts 2128 +306.2% 8646 ± 9% interrupts.CPU38.RES:Rescheduling_interrupts 1047 ± 4% +212.3% 3272 ± 9% interrupts.CPU39.CAL:Function_call_interrupts 160454 +372.5% 758119 interrupts.CPU39.LOC:Local_timer_interrupts 2095 +214.2% 6583 interrupts.CPU39.RES:Rescheduling_interrupts 1070 ± 11% +211.3% 3333 ± 8% interrupts.CPU4.CAL:Function_call_interrupts 160548 +372.3% 758250 interrupts.CPU4.LOC:Local_timer_interrupts 2130 ± 4% +285.3% 8209 interrupts.CPU4.RES:Rescheduling_interrupts 963.25 ± 17% +225.8% 3138 interrupts.CPU5.CAL:Function_call_interrupts 160994 +371.0% 758309 interrupts.CPU5.LOC:Local_timer_interrupts 2117 ± 2% +230.2% 6992 ± 6% interrupts.CPU5.RES:Rescheduling_interrupts 39.75 ± 2% +366.7% 185.50 interrupts.CPU6.94:IR-PCI-MSI.512000-edge.ahci[0000:00:1f.2] 1048 ± 13% +223.4% 3389 ± 6% interrupts.CPU6.CAL:Function_call_interrupts 160695 +372.0% 758502 interrupts.CPU6.LOC:Local_timer_interrupts 2143 ± 3% +280.7% 8158 interrupts.CPU6.RES:Rescheduling_interrupts 1073 ± 9% +226.0% 3500 interrupts.CPU7.CAL:Function_call_interrupts 160777 +371.3% 757691 interrupts.CPU7.LOC:Local_timer_interrupts 3248 ± 36% +111.7% 6876 ± 34% interrupts.CPU7.NMI:Non-maskable_interrupts 3248 ± 36% +111.7% 6876 ± 34% interrupts.CPU7.PMI:Performance_monitoring_interrupts 2175 +205.1% 6636 ± 2% interrupts.CPU7.RES:Rescheduling_interrupts 1045 ± 12% +196.7% 3101 interrupts.CPU8.CAL:Function_call_interrupts 160575 +372.3% 758457 interrupts.CPU8.LOC:Local_timer_interrupts 2188 ± 5% +277.1% 8252 ± 4% interrupts.CPU8.RES:Rescheduling_interrupts 1091 ± 9% +186.0% 3122 interrupts.CPU9.CAL:Function_call_interrupts 160626 +372.2% 758451 interrupts.CPU9.LOC:Local_timer_interrupts 5576 ± 40% -75.7% 1354 ± 99% interrupts.CPU9.NMI:Non-maskable_interrupts 5576 ± 40% -75.7% 1354 ± 99% interrupts.CPU9.PMI:Performance_monitoring_interrupts 2159 ± 2% +212.9% 6755 interrupts.CPU9.RES:Rescheduling_interrupts 6425227 +372.0% 30325627 interrupts.LOC:Local_timer_interrupts 86362 +258.6% 309674 interrupts.RES:Rescheduling_interrupts 198.25 ± 3% -33.4% 132.00 interrupts.TLB:TLB_shootdowns Disclaimer: Results have been estimated based on internal Intel analysis and are provided for informational purposes only. Any difference in system hardware or software design or configuration may affect actual performance. Thanks, Rong Chen [-- Attachment #2: config-5.1.0-rc3-00068-gfa3fe73 --] [-- Type: text/plain, Size: 193351 bytes --] # # Automatically generated file; DO NOT EDIT. # Linux/x86_64 5.1.0-rc3 Kernel Configuration # # # Compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 # CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=70300 CONFIG_CLANG_VERSION=0 CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_WARN_MAYBE_UNINITIALIZED=y CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_BUILD_SALT="" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_USELIB=y CONFIG_AUDIT=y CONFIG_HAVE_ARCH_AUDITSYSCALL=y CONFIG_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_GENERIC_IRQ_MIGRATION=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_SIM=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_ARCH_CLOCKSOURCE_INIT=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set # CONFIG_NO_HZ_IDLE is not set CONFIG_NO_HZ_FULL=y CONFIG_CONTEXT_TRACKING=y # CONFIG_CONTEXT_TRACKING_FORCE is not set CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting # CONFIG_VIRT_CPU_ACCOUNTING=y CONFIG_VIRT_CPU_ACCOUNTING_GEN=y # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_HAVE_SCHED_AVG_IRQ=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # CONFIG_PSI is not set CONFIG_CPU_ISOLATION=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TREE_SRCU=y CONFIG_TASKS_RCU=y CONFIG_RCU_STALL_COMMON=y CONFIG_RCU_NEED_SEGCBLIST=y CONFIG_RCU_NOCB_CPU=y CONFIG_BUILD_BIN2C=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=20 CONFIG_LOG_CPU_MAX_BUF_SHIFT=12 CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_ARCH_SUPPORTS_INT128=y CONFIG_NUMA_BALANCING=y CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y CONFIG_CGROUPS=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_MEMCG_SWAP=y CONFIG_MEMCG_SWAP_ENABLED=y CONFIG_MEMCG_KMEM=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CGROUP_WRITEBACK=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y CONFIG_RT_GROUP_SCHED=y CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_RDMA=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_HUGETLB=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_DEVICE=y CONFIG_CGROUP_CPUACCT=y CONFIG_CGROUP_PERF=y CONFIG_CGROUP_BPF=y # CONFIG_CGROUP_DEBUG is not set CONFIG_SOCK_CGROUP_DATA=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_CHECKPOINT_RESTORE=y CONFIG_SCHED_AUTOGROUP=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y CONFIG_RD_LZ4=y CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y CONFIG_UID16=y CONFIG_MULTIUSER=y CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_FHANDLE=y CONFIG_POSIX_TIMERS=y CONFIG_PRINTK=y CONFIG_PRINTK_NMI=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_FUTEX_PI=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_IO_URING=y CONFIG_ADVISE_SYSCALLS=y CONFIG_MEMBARRIER=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_ABSOLUTE_PERCPU=y CONFIG_KALLSYMS_BASE_RELATIVE=y CONFIG_BPF_SYSCALL=y CONFIG_BPF_JIT_ALWAYS_ON=y CONFIG_USERFAULTFD=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_RSEQ=y # CONFIG_DEBUG_RSEQ is not set CONFIG_EMBEDDED=y CONFIG_HAVE_PERF_EVENTS=y # CONFIG_PC104 is not set # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLUB_MEMCG_SYSFS_ON is not set # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_SLAB_MERGE_DEFAULT=y # CONFIG_SLAB_FREELIST_RANDOM is not set # CONFIG_SLAB_FREELIST_HARDENED is not set CONFIG_SLUB_CPU_PARTIAL=y CONFIG_SYSTEM_DATA_VERIFICATION=y CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_MMU=y CONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_FILTER_PGPROT=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=y CONFIG_X86_64_SMP=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_DYNAMIC_PHYSICAL_MASK=y CONFIG_PGTABLE_LEVELS=5 CONFIG_CC_HAS_SANE_STACKPROTECTOR=y # # Processor type and features # CONFIG_ZONE_DMA=y CONFIG_SMP=y CONFIG_X86_FEATURE_NAMES=y CONFIG_X86_X2APIC=y CONFIG_X86_MPPARSE=y # CONFIG_GOLDFISH is not set CONFIG_RETPOLINE=y # CONFIG_X86_CPU_RESCTRL is not set CONFIG_X86_EXTENDED_PLATFORM=y # CONFIG_X86_NUMACHIP is not set # CONFIG_X86_VSMP is not set CONFIG_X86_UV=y # CONFIG_X86_GOLDFISH is not set # CONFIG_X86_INTEL_MID is not set CONFIG_X86_INTEL_LPSS=y CONFIG_X86_AMD_PLATFORM_DEVICE=y CONFIG_IOSF_MBI=y # CONFIG_IOSF_MBI_DEBUG is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y # CONFIG_SCHED_OMIT_FRAME_POINTER is not set CONFIG_HYPERVISOR_GUEST=y CONFIG_PARAVIRT=y CONFIG_PARAVIRT_XXL=y # CONFIG_PARAVIRT_DEBUG is not set CONFIG_PARAVIRT_SPINLOCKS=y # CONFIG_QUEUED_LOCK_STAT is not set CONFIG_XEN=y CONFIG_XEN_PV=y CONFIG_XEN_PV_SMP=y # CONFIG_XEN_DOM0 is not set CONFIG_XEN_PVHVM=y CONFIG_XEN_PVHVM_SMP=y CONFIG_XEN_512GB=y CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set # CONFIG_XEN_PVH is not set CONFIG_KVM_GUEST=y # CONFIG_PVH is not set # CONFIG_KVM_DEBUG_FS is not set CONFIG_PARAVIRT_TIME_ACCOUNTING=y CONFIG_PARAVIRT_CLOCK=y # CONFIG_JAILHOUSE_GUEST is not set # CONFIG_MK8 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_MATOM is not set CONFIG_GENERIC_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y # CONFIG_PROCESSOR_SELECT is not set CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_HYGON=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_MAXSMP=y CONFIG_NR_CPUS_RANGE_BEGIN=8192 CONFIG_NR_CPUS_RANGE_END=8192 CONFIG_NR_CPUS_DEFAULT=8192 CONFIG_NR_CPUS=8192 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_SCHED_MC_PRIO=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MCE=y CONFIG_X86_MCELOG_LEGACY=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_X86_MCE_THRESHOLD=y CONFIG_X86_MCE_INJECT=m CONFIG_X86_THERMAL_VECTOR=y # # Performance monitoring # CONFIG_PERF_EVENTS_INTEL_UNCORE=y CONFIG_PERF_EVENTS_INTEL_RAPL=y CONFIG_PERF_EVENTS_INTEL_CSTATE=y # CONFIG_PERF_EVENTS_AMD_POWER is not set CONFIG_X86_16BIT=y CONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_I8K=m CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_5LEVEL=y CONFIG_X86_DIRECT_GBPAGES=y # CONFIG_X86_CPA_STATISTICS is not set CONFIG_ARCH_HAS_MEM_ENCRYPT=y CONFIG_AMD_MEM_ENCRYPT=y # CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set CONFIG_NUMA=y CONFIG_AMD_NUMA=y CONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y # CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y # CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64 CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=y CONFIG_X86_SMAP=y CONFIG_X86_INTEL_UMIP=y CONFIG_X86_INTEL_MPX=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_MIXED=y CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y CONFIG_KEXEC_VERIFY_SIG=y CONFIG_KEXEC_BZIMAGE_VERIFY_SIG=y CONFIG_CRASH_DUMP=y CONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=y CONFIG_RANDOMIZE_BASE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y # CONFIG_DEBUG_HOTPLUG_CPU0 is not set # CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y # CONFIG_LEGACY_VSYSCALL_NONE is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=y CONFIG_LIVEPATCH=y CONFIG_ARCH_HAS_ADD_PAGES=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y CONFIG_ARCH_ENABLE_THP_MIGRATION=y # # Power management and ACPI options # CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y # CONFIG_SUSPEND_SKIP_SYNC is not set CONFIG_HIBERNATE_CALLBACKS=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_PM_SLEEP=y CONFIG_PM_SLEEP_SMP=y # CONFIG_PM_AUTOSLEEP is not set # CONFIG_PM_WAKELOCKS is not set CONFIG_PM=y CONFIG_PM_DEBUG=y CONFIG_PM_ADVANCED_DEBUG=y # CONFIG_PM_TEST_SUSPEND is not set CONFIG_PM_SLEEP_DEBUG=y # CONFIG_DPM_WATCHDOG is not set CONFIG_PM_TRACE=y CONFIG_PM_TRACE_RTC=y CONFIG_PM_CLK=y # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set # CONFIG_ENERGY_MODEL is not set CONFIG_ARCH_SUPPORTS_ACPI=y CONFIG_ACPI=y CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y # CONFIG_ACPI_DEBUGGER is not set CONFIG_ACPI_SPCR_TABLE=y CONFIG_ACPI_LPIT=y CONFIG_ACPI_SLEEP=y # CONFIG_ACPI_PROCFS_POWER is not set CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y CONFIG_ACPI_EC_DEBUGFS=m CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y # CONFIG_ACPI_TAD is not set CONFIG_ACPI_DOCK=y CONFIG_ACPI_CPU_FREQ_PSS=y CONFIG_ACPI_PROCESSOR_CSTATE=y CONFIG_ACPI_PROCESSOR_IDLE=y CONFIG_ACPI_CPPC_LIB=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_IPMI=m CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y CONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=y CONFIG_ACPI_TABLE_UPGRADE=y # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_HOTPLUG_MEMORY=y CONFIG_ACPI_HOTPLUG_IOAPIC=y CONFIG_ACPI_SBS=m CONFIG_ACPI_HED=y CONFIG_ACPI_CUSTOM_METHOD=m CONFIG_ACPI_BGRT=y # CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set CONFIG_ACPI_NFIT=m # CONFIG_NFIT_SECURITY_DEBUG is not set CONFIG_HAVE_ACPI_APEI=y CONFIG_HAVE_ACPI_APEI_NMI=y CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=y CONFIG_ACPI_APEI_PCIEAER=y CONFIG_ACPI_APEI_MEMORY_FAILURE=y CONFIG_ACPI_APEI_EINJ=m CONFIG_ACPI_APEI_ERST_DEBUG=y # CONFIG_DPTF_POWER is not set CONFIG_ACPI_WATCHDOG=y CONFIG_ACPI_EXTLOG=m CONFIG_ACPI_ADXL=y # CONFIG_PMIC_OPREGION is not set # CONFIG_ACPI_CONFIGFS is not set CONFIG_X86_PM_TIMER=y CONFIG_SFI=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y # CONFIG_CPU_FREQ_STAT is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y # CONFIG_CPU_FREQ_GOV_SCHEDUTIL is not set # # CPU frequency scaling drivers # CONFIG_X86_INTEL_PSTATE=y CONFIG_X86_PCC_CPUFREQ=m CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_ACPI_CPUFREQ_CPB=y CONFIG_X86_POWERNOW_K8=m CONFIG_X86_AMD_FREQ_SENSITIVITY=m # CONFIG_X86_SPEEDSTEP_CENTRINO is not set CONFIG_X86_P4_CLOCKMOD=m # # shared options # CONFIG_X86_SPEEDSTEP_LIB=m # # CPU Idle # CONFIG_CPU_IDLE=y # CONFIG_CPU_IDLE_GOV_LADDER is not set CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_CPU_IDLE_GOV_TEO is not set CONFIG_INTEL_IDLE=y # # Bus options (PCI etc.) # CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_XEN=y CONFIG_MMCONF_FAM10H=y # CONFIG_PCI_CNB20LE_QUIRK is not set # CONFIG_ISA_BUS is not set CONFIG_ISA_DMA_API=y CONFIG_AMD_NB=y # CONFIG_X86_SYSFB is not set # # Binary Emulations # CONFIG_IA32_EMULATION=y # CONFIG_X86_X32 is not set CONFIG_COMPAT_32=y CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_X86_DEV_DMA_OPS=y CONFIG_HAVE_GENERIC_GUP=y # # Firmware Drivers # CONFIG_EDD=m # CONFIG_EDD_OFF is not set CONFIG_FIRMWARE_MEMMAP=y CONFIG_DMIID=y CONFIG_DMI_SYSFS=y CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m CONFIG_FW_CFG_SYSFS=y # CONFIG_FW_CFG_SYSFS_CMDLINE is not set # CONFIG_GOOGLE_FIRMWARE is not set # # EFI (Extensible Firmware Interface) Support # CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_VARS_PSTORE=y CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y CONFIG_EFI_RUNTIME_MAP=y # CONFIG_EFI_FAKE_MEMMAP is not set CONFIG_EFI_RUNTIME_WRAPPERS=y # CONFIG_EFI_BOOTLOADER_CONTROL is not set # CONFIG_EFI_CAPSULE_LOADER is not set # CONFIG_EFI_TEST is not set CONFIG_APPLE_PROPERTIES=y # CONFIG_RESET_ATTACK_MITIGATION is not set CONFIG_UEFI_CPER=y CONFIG_UEFI_CPER_X86=y CONFIG_EFI_DEV_PATH_PARSER=y CONFIG_EFI_EARLYCON=y # # Tegra firmware driver # CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_HAVE_KVM_IRQFD=y CONFIG_HAVE_KVM_IRQ_ROUTING=y CONFIG_HAVE_KVM_EVENTFD=y CONFIG_KVM_MMIO=y CONFIG_KVM_ASYNC_PF=y CONFIG_HAVE_KVM_MSI=y CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y CONFIG_KVM_VFIO=y CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y CONFIG_KVM_COMPAT=y CONFIG_HAVE_KVM_IRQ_BYPASS=y CONFIG_VIRTUALIZATION=y CONFIG_KVM=m CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m CONFIG_KVM_AMD_SEV=y CONFIG_KVM_MMU_AUDIT=y CONFIG_VHOST_NET=m # CONFIG_VHOST_SCSI is not set CONFIG_VHOST_VSOCK=m CONFIG_VHOST=m # CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set # # General architecture-dependent options # CONFIG_CRASH_CORE=y CONFIG_KEXEC_CORE=y CONFIG_HOTPLUG_SMT=y CONFIG_OPROFILE=m CONFIG_OPROFILE_EVENT_MULTIPLEX=y CONFIG_HAVE_OPROFILE=y CONFIG_OPROFILE_NMI_TIMER=y CONFIG_KPROBES=y CONFIG_JUMP_LABEL=y # CONFIG_STATIC_KEYS_SELFTEST is not set CONFIG_OPTPROBES=y CONFIG_KPROBES_ON_FTRACE=y CONFIG_UPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_ARCH_USE_BUILTIN_BSWAP=y CONFIG_KRETPROBES=y CONFIG_USER_RETURN_NOTIFIER=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_OPTPROBES=y CONFIG_HAVE_KPROBES_ON_FTRACE=y CONFIG_HAVE_FUNCTION_ERROR_INJECTION=y CONFIG_HAVE_NMI=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_CONTIGUOUS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_ARCH_HAS_FORTIFY_SOURCE=y CONFIG_ARCH_HAS_SET_MEMORY=y CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_RSEQ=y CONFIG_HAVE_FUNCTION_ARG_ACCESS_API=y CONFIG_HAVE_CLK=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y CONFIG_HAVE_PERF_EVENTS_NMI=y CONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=y CONFIG_HAVE_PERF_REGS=y CONFIG_HAVE_PERF_USER_STACK_DUMP=y CONFIG_HAVE_ARCH_JUMP_LABEL=y CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=y CONFIG_HAVE_RCU_TABLE_FREE=y CONFIG_HAVE_RCU_TABLE_INVALIDATE=y CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y CONFIG_HAVE_CMPXCHG_LOCAL=y CONFIG_HAVE_CMPXCHG_DOUBLE=y CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_SECCOMP_FILTER=y CONFIG_HAVE_ARCH_STACKLEAK=y CONFIG_HAVE_STACKPROTECTOR=y CONFIG_CC_HAS_STACKPROTECTOR_NONE=y CONFIG_STACKPROTECTOR=y CONFIG_STACKPROTECTOR_STRONG=y CONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=y CONFIG_HAVE_CONTEXT_TRACKING=y CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y CONFIG_HAVE_MOVE_PMD=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=y CONFIG_HAVE_ARCH_HUGE_VMAP=y CONFIG_HAVE_ARCH_SOFT_DIRTY=y CONFIG_HAVE_MOD_ARCH_SPECIFIC=y CONFIG_MODULES_USE_ELF_RELA=y CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y CONFIG_ARCH_HAS_ELF_RANDOMIZE=y CONFIG_HAVE_ARCH_MMAP_RND_BITS=y CONFIG_HAVE_EXIT_THREAD=y CONFIG_ARCH_MMAP_RND_BITS=28 CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=y CONFIG_ARCH_MMAP_RND_COMPAT_BITS=8 CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=y CONFIG_HAVE_COPY_THREAD_TLS=y CONFIG_HAVE_STACK_VALIDATION=y CONFIG_HAVE_RELIABLE_STACKTRACE=y CONFIG_OLD_SIGSUSPEND3=y CONFIG_COMPAT_OLD_SIGACTION=y CONFIG_COMPAT_32BIT_TIME=y CONFIG_HAVE_ARCH_VMAP_STACK=y CONFIG_VMAP_STACK=y CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y CONFIG_STRICT_KERNEL_RWX=y CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y CONFIG_STRICT_MODULE_RWX=y CONFIG_ARCH_HAS_REFCOUNT=y # CONFIG_REFCOUNT_FULL is not set CONFIG_HAVE_ARCH_PREL32_RELOCATIONS=y CONFIG_ARCH_USE_MEMREMAP_PROT=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y CONFIG_PLUGIN_HOSTCC="g++" CONFIG_HAVE_GCC_PLUGINS=y # CONFIG_GCC_PLUGINS is not set CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_FORCE_LOAD=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_MODULE_SIG=y # CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y # CONFIG_MODULE_SIG_SHA1 is not set # CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y # CONFIG_MODULE_SIG_SHA384 is not set # CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256" # CONFIG_MODULE_COMPRESS is not set # CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=y CONFIG_BLOCK=y CONFIG_BLK_SCSI_REQUEST=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_ZONED=y CONFIG_BLK_DEV_THROTTLING=y # CONFIG_BLK_DEV_THROTTLING_LOW is not set # CONFIG_BLK_CMDLINE_PARSER is not set # CONFIG_BLK_WBT is not set # CONFIG_BLK_CGROUP_IOLATENCY is not set CONFIG_BLK_DEBUG_FS=y CONFIG_BLK_DEBUG_FS_ZONED=y # CONFIG_BLK_SED_OPAL is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_AIX_PARTITION is not set CONFIG_OSF_PARTITION=y CONFIG_AMIGA_PARTITION=y # CONFIG_ATARI_PARTITION is not set CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y # CONFIG_LDM_PARTITION is not set CONFIG_SGI_PARTITION=y # CONFIG_ULTRIX_PARTITION is not set CONFIG_SUN_PARTITION=y CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y # CONFIG_SYSV68_PARTITION is not set # CONFIG_CMDLINE_PARTITION is not set CONFIG_BLOCK_COMPAT=y CONFIG_BLK_MQ_PCI=y CONFIG_BLK_MQ_VIRTIO=y CONFIG_BLK_MQ_RDMA=y CONFIG_BLK_PM=y # # IO Schedulers # CONFIG_MQ_IOSCHED_DEADLINE=y CONFIG_MQ_IOSCHED_KYBER=y # CONFIG_IOSCHED_BFQ is not set CONFIG_PREEMPT_NOTIFIERS=y CONFIG_PADATA=y CONFIG_ASN1=y CONFIG_INLINE_SPIN_UNLOCK_IRQ=y CONFIG_INLINE_READ_UNLOCK=y CONFIG_INLINE_READ_UNLOCK_IRQ=y CONFIG_INLINE_WRITE_UNLOCK=y CONFIG_INLINE_WRITE_UNLOCK_IRQ=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y CONFIG_LOCK_SPIN_ON_OWNER=y CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y CONFIG_QUEUED_SPINLOCKS=y CONFIG_ARCH_USE_QUEUED_RWLOCKS=y CONFIG_QUEUED_RWLOCKS=y CONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=y CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y CONFIG_FREEZER=y # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y CONFIG_ELFCORE=y CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y CONFIG_BINFMT_SCRIPT=y CONFIG_BINFMT_MISC=m CONFIG_COREDUMP=y # # Memory Management options # CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_MEMBLOCK_NODE_MAP=y CONFIG_ARCH_DISCARD_MEMBLOCK=y CONFIG_MEMORY_ISOLATION=y CONFIG_HAVE_BOOTMEM_INFO_NODE=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y # CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set CONFIG_MEMORY_HOTREMOVE=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MEMORY_BALLOON=y CONFIG_BALLOON_COMPACTION=y CONFIG_COMPACTION=y CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y CONFIG_HWPOISON_INJECT=m CONFIG_TRANSPARENT_HUGEPAGE=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y # CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set CONFIG_ARCH_WANTS_THP_SWAP=y CONFIG_THP_SWAP=y CONFIG_TRANSPARENT_HUGE_PAGECACHE=y CONFIG_CLEANCACHE=y CONFIG_FRONTSWAP=y CONFIG_CMA=y # CONFIG_CMA_DEBUG is not set # CONFIG_CMA_DEBUGFS is not set CONFIG_CMA_AREAS=7 CONFIG_MEM_SOFT_DIRTY=y CONFIG_ZSWAP=y CONFIG_ZPOOL=y CONFIG_ZBUD=y # CONFIG_Z3FOLD is not set CONFIG_ZSMALLOC=y # CONFIG_PGTABLE_MAPPING is not set # CONFIG_ZSMALLOC_STAT is not set CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_DEFERRED_STRUCT_PAGE_INIT=y CONFIG_IDLE_PAGE_TRACKING=y CONFIG_ARCH_HAS_ZONE_DEVICE=y CONFIG_ZONE_DEVICE=y CONFIG_ARCH_HAS_HMM=y CONFIG_MIGRATE_VMA_HELPER=y CONFIG_DEV_PAGEMAP_OPS=y CONFIG_HMM=y CONFIG_HMM_MIRROR=y # CONFIG_DEVICE_PRIVATE is not set # CONFIG_DEVICE_PUBLIC is not set CONFIG_FRAME_VECTOR=y CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y CONFIG_ARCH_HAS_PKEYS=y # CONFIG_PERCPU_STATS is not set # CONFIG_GUP_BENCHMARK is not set CONFIG_ARCH_HAS_PTE_SPECIAL=y CONFIG_NET=y CONFIG_COMPAT_NETLINK_MESSAGES=y CONFIG_NET_INGRESS=y CONFIG_NET_EGRESS=y CONFIG_SKB_EXTENSIONS=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_DIAG=m CONFIG_UNIX=y CONFIG_UNIX_SCM=y CONFIG_UNIX_DIAG=m # CONFIG_TLS is not set CONFIG_XFRM=y CONFIG_XFRM_ALGO=y CONFIG_XFRM_USER=y # CONFIG_XFRM_INTERFACE is not set CONFIG_XFRM_SUB_POLICY=y CONFIG_XFRM_MIGRATE=y CONFIG_XFRM_STATISTICS=y CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m CONFIG_NET_KEY_MIGRATE=y # CONFIG_SMC is not set # CONFIG_XDP_SOCKETS is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_FIB_TRIE_STATS=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y CONFIG_IP_ROUTE_CLASSID=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE_DEMUX=m CONFIG_NET_IP_TUNNEL=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y CONFIG_IP_MROUTE_COMMON=y CONFIG_IP_MROUTE=y CONFIG_IP_MROUTE_MULTIPLE_TABLES=y CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y CONFIG_SYN_COOKIES=y CONFIG_NET_IPVTI=m CONFIG_NET_UDP_TUNNEL=m CONFIG_NET_FOU=m CONFIG_NET_FOU_IP_TUNNELS=y CONFIG_INET_AH=m CONFIG_INET_ESP=m # CONFIG_INET_ESP_OFFLOAD is not set CONFIG_INET_IPCOMP=m CONFIG_INET_XFRM_TUNNEL=m CONFIG_INET_TUNNEL=m CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_DIAG=m CONFIG_INET_TCP_DIAG=m CONFIG_INET_UDP_DIAG=m # CONFIG_INET_RAW_DIAG is not set # CONFIG_INET_DIAG_DESTROY is not set CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m # CONFIG_TCP_CONG_NV is not set CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m CONFIG_TCP_CONG_DCTCP=m # CONFIG_TCP_CONG_CDG is not set # CONFIG_TCP_CONG_BBR is not set CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=y CONFIG_IPV6=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y CONFIG_IPV6_OPTIMISTIC_DAD=y CONFIG_INET6_AH=m CONFIG_INET6_ESP=m # CONFIG_INET6_ESP_OFFLOAD is not set CONFIG_INET6_IPCOMP=m CONFIG_IPV6_MIP6=m # CONFIG_IPV6_ILA is not set CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_VTI=m CONFIG_IPV6_SIT=m CONFIG_IPV6_SIT_6RD=y CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_GRE=m CONFIG_IPV6_FOU=m CONFIG_IPV6_FOU_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y # CONFIG_IPV6_SUBTREES is not set CONFIG_IPV6_MROUTE=y CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y CONFIG_IPV6_PIMSM_V2=y CONFIG_IPV6_SEG6_LWTUNNEL=y # CONFIG_IPV6_SEG6_HMAC is not set CONFIG_IPV6_SEG6_BPF=y CONFIG_NETLABEL=y CONFIG_NETWORK_SECMARK=y CONFIG_NET_PTP_CLASSIFY=y CONFIG_NETWORK_PHY_TIMESTAMPING=y CONFIG_NETFILTER=y CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=m # # Core Netfilter Configuration # CONFIG_NETFILTER_INGRESS=y CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_FAMILY_BRIDGE=y CONFIG_NETFILTER_FAMILY_ARP=y CONFIG_NETFILTER_NETLINK_ACCT=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NETFILTER_NETLINK_OSF=m CONFIG_NF_CONNTRACK=m CONFIG_NF_LOG_COMMON=m # CONFIG_NF_LOG_NETDEV is not set CONFIG_NETFILTER_CONNCOUNT=m CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_ZONES=y CONFIG_NF_CONNTRACK_PROCFS=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CONNTRACK_TIMEOUT=y CONFIG_NF_CONNTRACK_TIMESTAMP=y CONFIG_NF_CONNTRACK_LABELS=y CONFIG_NF_CT_PROTO_DCCP=y CONFIG_NF_CT_PROTO_GRE=y CONFIG_NF_CT_PROTO_SCTP=y CONFIG_NF_CT_PROTO_UDPLITE=y CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_BROADCAST=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_SNMP=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NF_CT_NETLINK_TIMEOUT=m # CONFIG_NETFILTER_NETLINK_GLUE_CT is not set CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_SIP=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_REDIRECT=y CONFIG_NF_NAT_MASQUERADE=y CONFIG_NETFILTER_SYNPROXY=m CONFIG_NF_TABLES=m # CONFIG_NF_TABLES_SET is not set # CONFIG_NF_TABLES_INET is not set # CONFIG_NF_TABLES_NETDEV is not set # CONFIG_NFT_NUMGEN is not set CONFIG_NFT_CT=m CONFIG_NFT_COUNTER=m # CONFIG_NFT_CONNLIMIT is not set CONFIG_NFT_LOG=m CONFIG_NFT_LIMIT=m CONFIG_NFT_MASQ=m CONFIG_NFT_REDIR=m # CONFIG_NFT_TUNNEL is not set # CONFIG_NFT_OBJREF is not set CONFIG_NFT_QUEUE=m # CONFIG_NFT_QUOTA is not set CONFIG_NFT_REJECT=m CONFIG_NFT_COMPAT=m CONFIG_NFT_HASH=m # CONFIG_NFT_XFRM is not set # CONFIG_NFT_SOCKET is not set # CONFIG_NFT_OSF is not set # CONFIG_NFT_TPROXY is not set # CONFIG_NF_FLOW_TABLE is not set CONFIG_NETFILTER_XTABLES=y # # Xtables combined modules # CONFIG_NETFILTER_XT_MARK=m CONFIG_NETFILTER_XT_CONNMARK=m CONFIG_NETFILTER_XT_SET=m # # Xtables targets # CONFIG_NETFILTER_XT_TARGET_AUDIT=m CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_CT=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m CONFIG_NETFILTER_XT_TARGET_HMARK=m CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m CONFIG_NETFILTER_XT_TARGET_LED=m CONFIG_NETFILTER_XT_TARGET_LOG=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_NAT=m CONFIG_NETFILTER_XT_TARGET_NETMAP=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NOTRACK=m CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_REDIRECT=m CONFIG_NETFILTER_XT_TARGET_TEE=m CONFIG_NETFILTER_XT_TARGET_TPROXY=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_SECMARK=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m # # Xtables matches # CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m CONFIG_NETFILTER_XT_MATCH_BPF=m CONFIG_NETFILTER_XT_MATCH_CGROUP=m CONFIG_NETFILTER_XT_MATCH_CLUSTER=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLABEL=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m CONFIG_NETFILTER_XT_MATCH_CPU=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ECN=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m # CONFIG_NETFILTER_XT_MATCH_IPCOMP is not set CONFIG_NETFILTER_XT_MATCH_IPRANGE=m CONFIG_NETFILTER_XT_MATCH_IPVS=m CONFIG_NETFILTER_XT_MATCH_L2TP=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_NFACCT=m CONFIG_NETFILTER_XT_MATCH_OSF=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_RECENT=m CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_SOCKET=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_IP_SET=m CONFIG_IP_SET_MAX=256 CONFIG_IP_SET_BITMAP_IP=m CONFIG_IP_SET_BITMAP_IPMAC=m CONFIG_IP_SET_BITMAP_PORT=m CONFIG_IP_SET_HASH_IP=m CONFIG_IP_SET_HASH_IPMARK=m CONFIG_IP_SET_HASH_IPPORT=m CONFIG_IP_SET_HASH_IPPORTIP=m CONFIG_IP_SET_HASH_IPPORTNET=m CONFIG_IP_SET_HASH_IPMAC=m CONFIG_IP_SET_HASH_MAC=m CONFIG_IP_SET_HASH_NETPORTNET=m CONFIG_IP_SET_HASH_NET=m CONFIG_IP_SET_HASH_NETNET=m CONFIG_IP_SET_HASH_NETPORT=m CONFIG_IP_SET_HASH_NETIFACE=m CONFIG_IP_SET_LIST_SET=m CONFIG_IP_VS=m CONFIG_IP_VS_IPV6=y # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_AH_ESP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y CONFIG_IP_VS_PROTO_SCTP=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m # CONFIG_IP_VS_FO is not set # CONFIG_IP_VS_OVF is not set CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m # CONFIG_IP_VS_MH is not set CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS SH scheduler # CONFIG_IP_VS_SH_TAB_BITS=8 # # IPVS MH scheduler # CONFIG_IP_VS_MH_TAB_INDEX=12 # # IPVS application helper # CONFIG_IP_VS_FTP=m CONFIG_IP_VS_NFCT=y CONFIG_IP_VS_PE_SIP=m # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=m CONFIG_NF_SOCKET_IPV4=m CONFIG_NF_TPROXY_IPV4=m # CONFIG_NF_TABLES_IPV4 is not set # CONFIG_NF_TABLES_ARP is not set CONFIG_NF_DUP_IPV4=m # CONFIG_NF_LOG_ARP is not set CONFIG_NF_LOG_IPV4=m CONFIG_NF_REJECT_IPV4=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_RPFILTER=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_SYNPROXY=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_SECURITY=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_SOCKET_IPV6=m CONFIG_NF_TPROXY_IPV6=m # CONFIG_NF_TABLES_IPV6 is not set CONFIG_NF_DUP_IPV6=m CONFIG_NF_REJECT_IPV6=m CONFIG_NF_LOG_IPV6=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_RPFILTER=m CONFIG_IP6_NF_MATCH_RT=m # CONFIG_IP6_NF_MATCH_SRH is not set CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_TARGET_SYNPROXY=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_SECURITY=m CONFIG_IP6_NF_NAT=m CONFIG_IP6_NF_TARGET_MASQUERADE=m CONFIG_IP6_NF_TARGET_NPT=m CONFIG_NF_DEFRAG_IPV6=m # CONFIG_NF_TABLES_BRIDGE is not set CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_NFLOG=m # CONFIG_BPFILTER is not set CONFIG_IP_DCCP=m CONFIG_INET_DCCP_DIAG=m # # DCCP CCIDs Configuration # # CONFIG_IP_DCCP_CCID2_DEBUG is not set CONFIG_IP_DCCP_CCID3=y # CONFIG_IP_DCCP_CCID3_DEBUG is not set CONFIG_IP_DCCP_TFRC_LIB=y # # DCCP Kernel Hacking # # CONFIG_IP_DCCP_DEBUG is not set CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y # CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m # CONFIG_RDS is not set # CONFIG_TIPC is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m # CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m # CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m # CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=m CONFIG_L2TP_DEBUGFS=m CONFIG_L2TP_V3=y CONFIG_L2TP_IP=m CONFIG_L2TP_ETH=m CONFIG_STP=m CONFIG_GARP=m CONFIG_MRP=m CONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y CONFIG_HAVE_NET_DSA=y # CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y # CONFIG_DECNET is not set CONFIG_LLC=m # CONFIG_LLC2 is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_PHONET is not set CONFIG_6LOWPAN=m # CONFIG_6LOWPAN_DEBUGFS is not set CONFIG_6LOWPAN_NHC=m CONFIG_6LOWPAN_NHC_DEST=m CONFIG_6LOWPAN_NHC_FRAGMENT=m CONFIG_6LOWPAN_NHC_HOP=m CONFIG_6LOWPAN_NHC_IPV6=m CONFIG_6LOWPAN_NHC_MOBILITY=m CONFIG_6LOWPAN_NHC_ROUTING=m CONFIG_6LOWPAN_NHC_UDP=m # CONFIG_6LOWPAN_GHC_EXT_HDR_HOP is not set # CONFIG_6LOWPAN_GHC_UDP is not set # CONFIG_6LOWPAN_GHC_ICMPV6 is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_DEST is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE is not set CONFIG_IEEE802154=m # CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=m CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_MULTIQ=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFB=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m # CONFIG_NET_SCH_CBS is not set # CONFIG_NET_SCH_ETF is not set # CONFIG_NET_SCH_TAPRIO is not set CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_DRR=m CONFIG_NET_SCH_MQPRIO=m # CONFIG_NET_SCH_SKBPRIO is not set CONFIG_NET_SCH_CHOKE=m CONFIG_NET_SCH_QFQ=m CONFIG_NET_SCH_CODEL=m CONFIG_NET_SCH_FQ_CODEL=m # CONFIG_NET_SCH_CAKE is not set CONFIG_NET_SCH_FQ=m # CONFIG_NET_SCH_HHF is not set # CONFIG_NET_SCH_PIE is not set CONFIG_NET_SCH_INGRESS=m CONFIG_NET_SCH_PLUG=m # CONFIG_NET_SCH_DEFAULT is not set # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m CONFIG_CLS_U32_PERF=y CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_CLS_CGROUP=y CONFIG_NET_CLS_BPF=m CONFIG_NET_CLS_FLOWER=m CONFIG_NET_CLS_MATCHALL=m CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m # CONFIG_NET_EMATCH_CANID is not set CONFIG_NET_EMATCH_IPSET=m # CONFIG_NET_EMATCH_IPT is not set CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_SAMPLE=m CONFIG_NET_ACT_IPT=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_ACT_SKBEDIT=m CONFIG_NET_ACT_CSUM=m CONFIG_NET_ACT_VLAN=m # CONFIG_NET_ACT_BPF is not set CONFIG_NET_ACT_CONNMARK=m CONFIG_NET_ACT_SKBMOD=m # CONFIG_NET_ACT_IFE is not set CONFIG_NET_ACT_TUNNEL_KEY=m CONFIG_NET_CLS_IND=y CONFIG_NET_SCH_FIFO=y CONFIG_DCB=y CONFIG_DNS_RESOLVER=m # CONFIG_BATMAN_ADV is not set CONFIG_OPENVSWITCH=m CONFIG_OPENVSWITCH_GRE=m CONFIG_OPENVSWITCH_VXLAN=m CONFIG_OPENVSWITCH_GENEVE=m CONFIG_VSOCKETS=m CONFIG_VSOCKETS_DIAG=m CONFIG_VMWARE_VMCI_VSOCKETS=m CONFIG_VIRTIO_VSOCKETS=m CONFIG_VIRTIO_VSOCKETS_COMMON=m CONFIG_HYPERV_VSOCKETS=m CONFIG_NETLINK_DIAG=m CONFIG_MPLS=y CONFIG_NET_MPLS_GSO=y # CONFIG_MPLS_ROUTING is not set CONFIG_NET_NSH=m # CONFIG_HSR is not set CONFIG_NET_SWITCHDEV=y CONFIG_NET_L3_MASTER_DEV=y # CONFIG_NET_NCSI is not set CONFIG_RPS=y CONFIG_RFS_ACCEL=y CONFIG_XPS=y # CONFIG_CGROUP_NET_PRIO is not set CONFIG_CGROUP_NET_CLASSID=y CONFIG_NET_RX_BUSY_POLL=y CONFIG_BQL=y CONFIG_BPF_JIT=y CONFIG_BPF_STREAM_PARSER=y CONFIG_NET_FLOW_LIMIT=y # # Network testing # CONFIG_NET_PKTGEN=m CONFIG_NET_DROP_MONITOR=y # CONFIG_HAMRADIO is not set CONFIG_CAN=m CONFIG_CAN_RAW=m CONFIG_CAN_BCM=m CONFIG_CAN_GW=m # # CAN Device Drivers # CONFIG_CAN_VCAN=m # CONFIG_CAN_VXCAN is not set CONFIG_CAN_SLCAN=m CONFIG_CAN_DEV=m CONFIG_CAN_CALC_BITTIMING=y CONFIG_CAN_C_CAN=m CONFIG_CAN_C_CAN_PLATFORM=m CONFIG_CAN_C_CAN_PCI=m CONFIG_CAN_CC770=m # CONFIG_CAN_CC770_ISA is not set CONFIG_CAN_CC770_PLATFORM=m # CONFIG_CAN_IFI_CANFD is not set # CONFIG_CAN_M_CAN is not set # CONFIG_CAN_PEAK_PCIEFD is not set CONFIG_CAN_SJA1000=m # CONFIG_CAN_SJA1000_ISA is not set CONFIG_CAN_SJA1000_PLATFORM=m CONFIG_CAN_EMS_PCI=m CONFIG_CAN_PEAK_PCI=m CONFIG_CAN_PEAK_PCIEC=y CONFIG_CAN_KVASER_PCI=m CONFIG_CAN_PLX_PCI=m CONFIG_CAN_SOFTING=m # # CAN SPI interfaces # # CONFIG_CAN_HI311X is not set # CONFIG_CAN_MCP251X is not set # # CAN USB interfaces # CONFIG_CAN_8DEV_USB=m CONFIG_CAN_EMS_USB=m CONFIG_CAN_ESD_USB2=m # CONFIG_CAN_GS_USB is not set CONFIG_CAN_KVASER_USB=m # CONFIG_CAN_MCBA_USB is not set CONFIG_CAN_PEAK_USB=m # CONFIG_CAN_UCAN is not set # CONFIG_CAN_DEBUG_DEVICES is not set CONFIG_BT=m CONFIG_BT_BREDR=y CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_CMTP=m CONFIG_BT_HIDP=m CONFIG_BT_HS=y CONFIG_BT_LE=y # CONFIG_BT_6LOWPAN is not set # CONFIG_BT_LEDS is not set # CONFIG_BT_SELFTEST is not set CONFIG_BT_DEBUGFS=y # # Bluetooth device drivers # CONFIG_BT_INTEL=m CONFIG_BT_BCM=m CONFIG_BT_RTL=m CONFIG_BT_HCIBTUSB=m # CONFIG_BT_HCIBTUSB_AUTOSUSPEND is not set CONFIG_BT_HCIBTUSB_BCM=y CONFIG_BT_HCIBTUSB_RTL=y CONFIG_BT_HCIBTSDIO=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_ATH3K=y # CONFIG_BT_HCIUART_INTEL is not set # CONFIG_BT_HCIUART_AG6XX is not set # CONFIG_BT_HCIUART_MRVL is not set CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m CONFIG_BT_HCIBFUSB=m CONFIG_BT_HCIVHCI=m CONFIG_BT_MRVL=m CONFIG_BT_MRVL_SDIO=m CONFIG_BT_ATH3K=m # CONFIG_AF_RXRPC is not set # CONFIG_AF_KCM is not set CONFIG_STREAM_PARSER=y CONFIG_FIB_RULES=y CONFIG_WIRELESS=y CONFIG_WIRELESS_EXT=y CONFIG_WEXT_CORE=y CONFIG_WEXT_PROC=y CONFIG_WEXT_PRIV=y CONFIG_CFG80211=m # CONFIG_NL80211_TESTMODE is not set # CONFIG_CFG80211_DEVELOPER_WARNINGS is not set # CONFIG_CFG80211_CERTIFICATION_ONUS is not set CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y CONFIG_CFG80211_DEFAULT_PS=y # CONFIG_CFG80211_DEBUGFS is not set CONFIG_CFG80211_CRDA_SUPPORT=y CONFIG_CFG80211_WEXT=y CONFIG_LIB80211=m # CONFIG_LIB80211_DEBUG is not set CONFIG_MAC80211=m CONFIG_MAC80211_HAS_RC=y CONFIG_MAC80211_RC_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel_ht" CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y # CONFIG_MAC80211_MESSAGE_TRACING is not set # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_MAC80211_STA_HASH_MAX_SIZE=0 # CONFIG_WIMAX is not set CONFIG_RFKILL=m CONFIG_RFKILL_LEDS=y CONFIG_RFKILL_INPUT=y # CONFIG_RFKILL_GPIO is not set CONFIG_NET_9P=y CONFIG_NET_9P_VIRTIO=y # CONFIG_NET_9P_XEN is not set # CONFIG_NET_9P_RDMA is not set # CONFIG_NET_9P_DEBUG is not set # CONFIG_CAIF is not set CONFIG_CEPH_LIB=m # CONFIG_CEPH_LIB_PRETTYDEBUG is not set CONFIG_CEPH_LIB_USE_DNS_RESOLVER=y # CONFIG_NFC is not set CONFIG_PSAMPLE=m # CONFIG_NET_IFE is not set CONFIG_LWTUNNEL=y CONFIG_LWTUNNEL_BPF=y CONFIG_DST_CACHE=y CONFIG_GRO_CELLS=y CONFIG_NET_SOCK_MSG=y # CONFIG_NET_DEVLINK is not set CONFIG_PAGE_POOL=y CONFIG_FAILOVER=m CONFIG_HAVE_EBPF_JIT=y # # Device Drivers # CONFIG_HAVE_EISA=y # CONFIG_EISA is not set CONFIG_HAVE_PCI=y CONFIG_PCI=y CONFIG_PCI_DOMAINS=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y CONFIG_PCIEAER_INJECT=m CONFIG_PCIE_ECRC=y CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set CONFIG_PCIEASPM_DEFAULT=y # CONFIG_PCIEASPM_POWERSAVE is not set # CONFIG_PCIEASPM_POWER_SUPERSAVE is not set # CONFIG_PCIEASPM_PERFORMANCE is not set CONFIG_PCIE_PME=y # CONFIG_PCIE_DPC is not set # CONFIG_PCIE_PTM is not set CONFIG_PCI_MSI=y CONFIG_PCI_MSI_IRQ_DOMAIN=y CONFIG_PCI_QUIRKS=y # CONFIG_PCI_DEBUG is not set # CONFIG_PCI_REALLOC_ENABLE_AUTO is not set CONFIG_PCI_STUB=y # CONFIG_PCI_PF_STUB is not set # CONFIG_XEN_PCIDEV_FRONTEND is not set CONFIG_PCI_ATS=y CONFIG_PCI_LOCKLESS_CONFIG=y CONFIG_PCI_IOV=y CONFIG_PCI_PRI=y CONFIG_PCI_PASID=y # CONFIG_PCI_P2PDMA is not set CONFIG_PCI_LABEL=y CONFIG_PCI_HYPERV=m CONFIG_HOTPLUG_PCI=y CONFIG_HOTPLUG_PCI_ACPI=y CONFIG_HOTPLUG_PCI_ACPI_IBM=m # CONFIG_HOTPLUG_PCI_CPCI is not set CONFIG_HOTPLUG_PCI_SHPC=y # # PCI controller drivers # # # Cadence PCIe controllers support # CONFIG_VMD=y # # DesignWare PCI Core Support # # CONFIG_PCIE_DW_PLAT_HOST is not set # CONFIG_PCI_MESON is not set # # PCI Endpoint # # CONFIG_PCI_ENDPOINT is not set # # PCI switch controller drivers # # CONFIG_PCI_SW_SWITCHTEC is not set CONFIG_PCCARD=y # CONFIG_PCMCIA is not set CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_YENTA_O2=y CONFIG_YENTA_RICOH=y CONFIG_YENTA_TI=y CONFIG_YENTA_ENE_TUNE=y CONFIG_YENTA_TOSHIBA=y # CONFIG_RAPIDIO is not set # # Generic Driver Options # CONFIG_UEVENT_HELPER=y CONFIG_UEVENT_HELPER_PATH="" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # # Firmware loader # CONFIG_FW_LOADER=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y CONFIG_WANT_DEV_COREDUMP=y CONFIG_ALLOW_DEV_COREDUMP=y CONFIG_DEV_COREDUMP=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set # CONFIG_TEST_ASYNC_DRIVER_PROBE is not set CONFIG_SYS_HYPERVISOR=y CONFIG_GENERIC_CPU_AUTOPROBE=y CONFIG_GENERIC_CPU_VULNERABILITIES=y CONFIG_REGMAP=y CONFIG_REGMAP_I2C=y CONFIG_REGMAP_SPI=y CONFIG_REGMAP_IRQ=y CONFIG_DMA_SHARED_BUFFER=y # CONFIG_DMA_FENCE_TRACE is not set # # Bus devices # CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y # CONFIG_GNSS is not set CONFIG_MTD=m # CONFIG_MTD_TESTS is not set # CONFIG_MTD_CMDLINE_PARTS is not set # CONFIG_MTD_AR7_PARTS is not set # # Partition parsers # # CONFIG_MTD_REDBOOT_PARTS is not set # # User Modules And Translation Layers # CONFIG_MTD_BLKDEVS=m CONFIG_MTD_BLOCK=m # CONFIG_MTD_BLOCK_RO is not set # CONFIG_FTL is not set # CONFIG_NFTL is not set # CONFIG_INFTL is not set # CONFIG_RFD_FTL is not set # CONFIG_SSFDC is not set # CONFIG_SM_FTL is not set # CONFIG_MTD_OOPS is not set # CONFIG_MTD_SWAP is not set # CONFIG_MTD_PARTITIONED_MASTER is not set # # RAM/ROM/Flash chip drivers # # CONFIG_MTD_CFI is not set # CONFIG_MTD_JEDECPROBE is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set # CONFIG_MTD_ABSENT is not set # # Mapping drivers for chip access # # CONFIG_MTD_COMPLEX_MAPPINGS is not set # CONFIG_MTD_INTEL_VR_NOR is not set # CONFIG_MTD_PLATRAM is not set # # Self-contained MTD device drivers # # CONFIG_MTD_PMC551 is not set # CONFIG_MTD_DATAFLASH is not set # CONFIG_MTD_MCHP23K256 is not set # CONFIG_MTD_SST25L is not set # CONFIG_MTD_SLRAM is not set # CONFIG_MTD_PHRAM is not set # CONFIG_MTD_MTDRAM is not set # CONFIG_MTD_BLOCK2MTD is not set # # Disk-On-Chip Device Drivers # # CONFIG_MTD_DOCG3 is not set # CONFIG_MTD_ONENAND is not set # CONFIG_MTD_NAND is not set # CONFIG_MTD_SPI_NAND is not set # # LPDDR & LPDDR2 PCM memory drivers # # CONFIG_MTD_LPDDR is not set # CONFIG_MTD_SPI_NOR is not set CONFIG_MTD_UBI=m CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_LIMIT=20 # CONFIG_MTD_UBI_FASTMAP is not set # CONFIG_MTD_UBI_GLUEBI is not set # CONFIG_MTD_UBI_BLOCK is not set # CONFIG_OF is not set CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_SERIAL=m # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AX88796 is not set CONFIG_PARPORT_1284=y CONFIG_PARPORT_NOT_PC=y CONFIG_PNP=y # CONFIG_PNP_DEBUG_MESSAGES is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_NULL_BLK=m CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=y CONFIG_BLK_DEV_FD=m CONFIG_CDROM=m # CONFIG_PARIDE is not set CONFIG_BLK_DEV_PCIESSD_MTIP32XX=m # CONFIG_ZRAM is not set # CONFIG_BLK_DEV_UMEM is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_DRBD is not set CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_SKD is not set CONFIG_BLK_DEV_SX8=m CONFIG_BLK_DEV_RAM=m CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=16384 CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set CONFIG_ATA_OVER_ETH=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=y # CONFIG_VIRTIO_BLK_SCSI is not set CONFIG_BLK_DEV_RBD=m # CONFIG_BLK_DEV_RSXX is not set # # NVME Support # CONFIG_NVME_CORE=m CONFIG_BLK_DEV_NVME=m CONFIG_NVME_MULTIPATH=y CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m # CONFIG_NVME_TCP is not set CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m CONFIG_NVME_TARGET_FCLOOP=m # CONFIG_NVME_TARGET_TCP is not set # # Misc devices # CONFIG_SENSORS_LIS3LV02D=m # CONFIG_AD525X_DPOT is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set CONFIG_SGI_IOC4=m CONFIG_TIFM_CORE=m CONFIG_TIFM_7XX1=m # CONFIG_ICS932S401 is not set CONFIG_ENCLOSURE_SERVICES=m CONFIG_SGI_XP=m CONFIG_HP_ILO=m CONFIG_SGI_GRU=m # CONFIG_SGI_GRU_DEBUG is not set CONFIG_APDS9802ALS=m CONFIG_ISL29003=m CONFIG_ISL29020=m CONFIG_SENSORS_TSL2550=m CONFIG_SENSORS_BH1770=m CONFIG_SENSORS_APDS990X=m # CONFIG_HMC6352 is not set # CONFIG_DS1682 is not set CONFIG_VMWARE_BALLOON=m # CONFIG_USB_SWITCH_FSA9480 is not set # CONFIG_LATTICE_ECP3_CONFIG is not set # CONFIG_SRAM is not set # CONFIG_PCI_ENDPOINT_TEST is not set CONFIG_PVPANIC=y # CONFIG_C2PORT is not set # # EEPROM support # CONFIG_EEPROM_AT24=m # CONFIG_EEPROM_AT25 is not set CONFIG_EEPROM_LEGACY=m CONFIG_EEPROM_MAX6875=m CONFIG_EEPROM_93CX6=m # CONFIG_EEPROM_93XX46 is not set # CONFIG_EEPROM_IDT_89HPESX is not set # CONFIG_EEPROM_EE1004 is not set CONFIG_CB710_CORE=m # CONFIG_CB710_DEBUG is not set CONFIG_CB710_DEBUG_ASSUMPTIONS=y # # Texas Instruments shared transport line discipline # # CONFIG_TI_ST is not set CONFIG_SENSORS_LIS3_I2C=m CONFIG_ALTERA_STAPL=m CONFIG_INTEL_MEI=m CONFIG_INTEL_MEI_ME=m # CONFIG_INTEL_MEI_TXE is not set # CONFIG_INTEL_MEI_HDCP is not set CONFIG_VMWARE_VMCI=m # # Intel MIC & related support # # # Intel MIC Bus Driver # # CONFIG_INTEL_MIC_BUS is not set # # SCIF Bus Driver # # CONFIG_SCIF_BUS is not set # # VOP Bus Driver # # CONFIG_VOP_BUS is not set # # Intel MIC Host Driver # # # Intel MIC Card Driver # # # SCIF Driver # # # Intel MIC Coprocessor State Management (COSM) Drivers # # # VOP Driver # # CONFIG_GENWQE is not set # CONFIG_ECHO is not set # CONFIG_MISC_ALCOR_PCI is not set # CONFIG_MISC_RTSX_PCI is not set # CONFIG_MISC_RTSX_USB is not set # CONFIG_HABANA_AI is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_SCSI_MOD=y CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=m CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=m CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=m CONFIG_CHR_DEV_SCH=m CONFIG_SCSI_ENCLOSURE=m CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_SCAN_ASYNC=y # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=m CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_ISCSI_ATTRS=m CONFIG_SCSI_SAS_ATTRS=m CONFIG_SCSI_SAS_LIBSAS=m CONFIG_SCSI_SAS_ATA=y CONFIG_SCSI_SAS_HOST_SMP=y CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m CONFIG_ISCSI_BOOT_SYSFS=m CONFIG_SCSI_CXGB3_ISCSI=m CONFIG_SCSI_CXGB4_ISCSI=m CONFIG_SCSI_BNX2_ISCSI=m CONFIG_SCSI_BNX2X_FCOE=m CONFIG_BE2ISCSI=m # CONFIG_BLK_DEV_3W_XXXX_RAID is not set CONFIG_SCSI_HPSA=m CONFIG_SCSI_3W_9XXX=m CONFIG_SCSI_3W_SAS=m # CONFIG_SCSI_ACARD is not set CONFIG_SCSI_AACRAID=m # CONFIG_SCSI_AIC7XXX is not set CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=4 CONFIG_AIC79XX_RESET_DELAY_MS=15000 # CONFIG_AIC79XX_DEBUG_ENABLE is not set CONFIG_AIC79XX_DEBUG_MASK=0 # CONFIG_AIC79XX_REG_PRETTY_PRINT is not set # CONFIG_SCSI_AIC94XX is not set CONFIG_SCSI_MVSAS=m # CONFIG_SCSI_MVSAS_DEBUG is not set CONFIG_SCSI_MVSAS_TASKLET=y CONFIG_SCSI_MVUMI=m # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set CONFIG_SCSI_ARCMSR=m # CONFIG_SCSI_ESAS2R is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_MEGARAID_SAS=m CONFIG_SCSI_MPT3SAS=m CONFIG_SCSI_MPT2SAS_MAX_SGE=128 CONFIG_SCSI_MPT3SAS_MAX_SGE=128 CONFIG_SCSI_MPT2SAS=m CONFIG_SCSI_SMARTPQI=m CONFIG_SCSI_UFSHCD=m CONFIG_SCSI_UFSHCD_PCI=m # CONFIG_SCSI_UFS_DWC_TC_PCI is not set # CONFIG_SCSI_UFSHCD_PLATFORM is not set # CONFIG_SCSI_UFS_BSG is not set CONFIG_SCSI_HPTIOP=m # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_MYRB is not set # CONFIG_SCSI_MYRS is not set CONFIG_VMWARE_PVSCSI=m # CONFIG_XEN_SCSI_FRONTEND is not set CONFIG_HYPERV_STORAGE=m CONFIG_LIBFC=m CONFIG_LIBFCOE=m CONFIG_FCOE=m CONFIG_FCOE_FNIC=m # CONFIG_SCSI_SNIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_GDTH is not set CONFIG_SCSI_ISCI=m # CONFIG_SCSI_IPS is not set CONFIG_SCSI_INITIO=m # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_PPA is not set # CONFIG_SCSI_IMM is not set CONFIG_SCSI_STEX=m # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA_FC=m CONFIG_TCM_QLA2XXX=m # CONFIG_TCM_QLA2XXX_DEBUG is not set CONFIG_SCSI_QLA_ISCSI=m CONFIG_QEDI=m CONFIG_QEDF=m # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_AM53C974 is not set # CONFIG_SCSI_WD719X is not set CONFIG_SCSI_DEBUG=m CONFIG_SCSI_PMCRAID=m CONFIG_SCSI_PM8001=m CONFIG_SCSI_BFA_FC=m CONFIG_SCSI_VIRTIO=m CONFIG_SCSI_CHELSIO_FCOE=m CONFIG_SCSI_DH=y CONFIG_SCSI_DH_RDAC=y CONFIG_SCSI_DH_HP_SW=y CONFIG_SCSI_DH_EMC=y CONFIG_SCSI_DH_ALUA=y CONFIG_ATA=m CONFIG_ATA_VERBOSE_ERROR=y CONFIG_ATA_ACPI=y # CONFIG_SATA_ZPODD is not set CONFIG_SATA_PMP=y # # Controllers with non-SFF native interface # CONFIG_SATA_AHCI=m CONFIG_SATA_MOBILE_LPM_POLICY=0 CONFIG_SATA_AHCI_PLATFORM=m # CONFIG_SATA_INIC162X is not set CONFIG_SATA_ACARD_AHCI=m CONFIG_SATA_SIL24=m CONFIG_ATA_SFF=y # # SFF controllers with custom DMA interface # CONFIG_PDC_ADMA=m CONFIG_SATA_QSTOR=m CONFIG_SATA_SX4=m CONFIG_ATA_BMDMA=y # # SATA SFF controllers with BMDMA # CONFIG_ATA_PIIX=m # CONFIG_SATA_DWC is not set CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_SVW=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m # # PATA SFF controllers with BMDMA # CONFIG_PATA_ALI=m CONFIG_PATA_AMD=m CONFIG_PATA_ARTOP=m CONFIG_PATA_ATIIXP=m CONFIG_PATA_ATP867X=m CONFIG_PATA_CMD64X=m # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set CONFIG_PATA_HPT366=m CONFIG_PATA_HPT37X=m CONFIG_PATA_HPT3X2N=m CONFIG_PATA_HPT3X3=m # CONFIG_PATA_HPT3X3_DMA is not set CONFIG_PATA_IT8213=m CONFIG_PATA_IT821X=m CONFIG_PATA_JMICRON=m CONFIG_PATA_MARVELL=m CONFIG_PATA_NETCELL=m CONFIG_PATA_NINJA32=m # CONFIG_PATA_NS87415 is not set CONFIG_PATA_OLDPIIX=m # CONFIG_PATA_OPTIDMA is not set CONFIG_PATA_PDC2027X=m CONFIG_PATA_PDC_OLD=m # CONFIG_PATA_RADISYS is not set CONFIG_PATA_RDC=m CONFIG_PATA_SCH=m CONFIG_PATA_SERVERWORKS=m CONFIG_PATA_SIL680=m CONFIG_PATA_SIS=m CONFIG_PATA_TOSHIBA=m # CONFIG_PATA_TRIFLEX is not set CONFIG_PATA_VIA=m # CONFIG_PATA_WINBOND is not set # # PIO-only SFF controllers # # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_PLATFORM is not set # CONFIG_PATA_RZ1000 is not set # # Generic fallback / legacy drivers # CONFIG_PATA_ACPI=m CONFIG_ATA_GENERIC=m # CONFIG_PATA_LEGACY is not set CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m # CONFIG_MD_CLUSTER is not set # CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=m CONFIG_DM_DEBUG=y CONFIG_DM_BUFIO=m # CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m # CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=m CONFIG_DM_CACHE_SMQ=m # CONFIG_DM_WRITECACHE is not set CONFIG_DM_ERA=m CONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=m CONFIG_DM_RAID=m CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m CONFIG_DM_DELAY=m CONFIG_DM_UEVENT=y CONFIG_DM_FLAKEY=m CONFIG_DM_VERITY=m # CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=m CONFIG_DM_LOG_WRITES=m # CONFIG_DM_INTEGRITY is not set # CONFIG_DM_ZONED is not set CONFIG_TARGET_CORE=m CONFIG_TCM_IBLOCK=m CONFIG_TCM_FILEIO=m CONFIG_TCM_PSCSI=m CONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=m CONFIG_TCM_FC=m CONFIG_ISCSI_TARGET=m CONFIG_ISCSI_TARGET_CXGB4=m # CONFIG_SBP_TARGET is not set CONFIG_FUSION=y CONFIG_FUSION_SPI=m # CONFIG_FUSION_FC is not set CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=m CONFIG_FUSION_LOGGING=y # # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_SBP2=m CONFIG_FIREWIRE_NET=m # CONFIG_FIREWIRE_NOSY is not set CONFIG_MACINTOSH_DRIVERS=y CONFIG_MAC_EMUMOUSEBTN=y CONFIG_NETDEVICES=y CONFIG_MII=y CONFIG_NET_CORE=y CONFIG_BONDING=m CONFIG_DUMMY=m # CONFIG_EQUALIZER is not set CONFIG_NET_FC=y CONFIG_IFB=m CONFIG_NET_TEAM=m CONFIG_NET_TEAM_MODE_BROADCAST=m CONFIG_NET_TEAM_MODE_ROUNDROBIN=m CONFIG_NET_TEAM_MODE_RANDOM=m CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m CONFIG_NET_TEAM_MODE_LOADBALANCE=m CONFIG_MACVLAN=m CONFIG_MACVTAP=m # CONFIG_IPVLAN is not set CONFIG_VXLAN=m CONFIG_GENEVE=m # CONFIG_GTP is not set CONFIG_MACSEC=y CONFIG_NETCONSOLE=m CONFIG_NETCONSOLE_DYNAMIC=y CONFIG_NETPOLL=y CONFIG_NET_POLL_CONTROLLER=y CONFIG_NTB_NETDEV=m CONFIG_TUN=m CONFIG_TAP=m # CONFIG_TUN_VNET_CROSS_LE is not set CONFIG_VETH=m CONFIG_VIRTIO_NET=m CONFIG_NLMON=m CONFIG_NET_VRF=y CONFIG_VSOCKMON=m # CONFIG_ARCNET is not set # CONFIG_ATM_DRIVERS is not set # # CAIF transport drivers # # # Distributed Switch Architecture drivers # CONFIG_ETHERNET=y CONFIG_MDIO=y # CONFIG_NET_VENDOR_3COM is not set # CONFIG_NET_VENDOR_ADAPTEC is not set CONFIG_NET_VENDOR_AGERE=y # CONFIG_ET131X is not set CONFIG_NET_VENDOR_ALACRITECH=y # CONFIG_SLICOSS is not set # CONFIG_NET_VENDOR_ALTEON is not set # CONFIG_ALTERA_TSE is not set CONFIG_NET_VENDOR_AMAZON=y CONFIG_ENA_ETHERNET=m CONFIG_NET_VENDOR_AMD=y CONFIG_AMD8111_ETH=m CONFIG_PCNET32=m CONFIG_AMD_XGBE=m # CONFIG_AMD_XGBE_DCB is not set CONFIG_AMD_XGBE_HAVE_ECC=y CONFIG_NET_VENDOR_AQUANTIA=y CONFIG_AQTION=m CONFIG_NET_VENDOR_ARC=y CONFIG_NET_VENDOR_ATHEROS=y CONFIG_ATL2=m CONFIG_ATL1=m CONFIG_ATL1E=m CONFIG_ATL1C=m CONFIG_ALX=m CONFIG_NET_VENDOR_AURORA=y # CONFIG_AURORA_NB8800 is not set CONFIG_NET_VENDOR_BROADCOM=y CONFIG_B44=m CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y # CONFIG_BCMGENET is not set CONFIG_BNX2=m CONFIG_CNIC=m CONFIG_TIGON3=y CONFIG_TIGON3_HWMON=y CONFIG_BNX2X=m CONFIG_BNX2X_SRIOV=y # CONFIG_SYSTEMPORT is not set CONFIG_BNXT=m CONFIG_BNXT_SRIOV=y CONFIG_BNXT_FLOWER_OFFLOAD=y CONFIG_BNXT_DCB=y CONFIG_BNXT_HWMON=y CONFIG_NET_VENDOR_BROCADE=y CONFIG_BNA=m CONFIG_NET_VENDOR_CADENCE=y CONFIG_MACB=m CONFIG_MACB_USE_HWSTAMP=y # CONFIG_MACB_PCI is not set CONFIG_NET_VENDOR_CAVIUM=y # CONFIG_THUNDER_NIC_PF is not set # CONFIG_THUNDER_NIC_VF is not set # CONFIG_THUNDER_NIC_BGX is not set # CONFIG_THUNDER_NIC_RGX is not set CONFIG_CAVIUM_PTP=y CONFIG_LIQUIDIO=m CONFIG_LIQUIDIO_VF=m CONFIG_NET_VENDOR_CHELSIO=y # CONFIG_CHELSIO_T1 is not set CONFIG_CHELSIO_T3=m CONFIG_CHELSIO_T4=m # CONFIG_CHELSIO_T4_DCB is not set CONFIG_CHELSIO_T4VF=m CONFIG_CHELSIO_LIB=m CONFIG_NET_VENDOR_CISCO=y CONFIG_ENIC=m CONFIG_NET_VENDOR_CORTINA=y # CONFIG_CX_ECAT is not set CONFIG_DNET=m CONFIG_NET_VENDOR_DEC=y CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_DE2104X_DSL=0 CONFIG_TULIP=y # CONFIG_TULIP_MWI is not set CONFIG_TULIP_MMIO=y # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_ULI526X=m CONFIG_PCMCIA_XIRCOM=m # CONFIG_NET_VENDOR_DLINK is not set CONFIG_NET_VENDOR_EMULEX=y CONFIG_BE2NET=m CONFIG_BE2NET_HWMON=y CONFIG_BE2NET_BE2=y CONFIG_BE2NET_BE3=y CONFIG_BE2NET_LANCER=y CONFIG_BE2NET_SKYHAWK=y CONFIG_NET_VENDOR_EZCHIP=y # CONFIG_NET_VENDOR_HP is not set CONFIG_NET_VENDOR_HUAWEI=y # CONFIG_HINIC is not set # CONFIG_NET_VENDOR_I825XX is not set CONFIG_NET_VENDOR_INTEL=y # CONFIG_E100 is not set CONFIG_E1000=y CONFIG_E1000E=y CONFIG_E1000E_HWTS=y CONFIG_IGB=y CONFIG_IGB_HWMON=y CONFIG_IGBVF=m CONFIG_IXGB=y CONFIG_IXGBE=y CONFIG_IXGBE_HWMON=y CONFIG_IXGBE_DCB=y CONFIG_IXGBEVF=m CONFIG_I40E=m CONFIG_I40E_DCB=y CONFIG_IAVF=m CONFIG_I40EVF=m # CONFIG_ICE is not set CONFIG_FM10K=m # CONFIG_IGC is not set CONFIG_JME=m CONFIG_NET_VENDOR_MARVELL=y CONFIG_MVMDIO=m CONFIG_SKGE=y # CONFIG_SKGE_DEBUG is not set CONFIG_SKGE_GENESIS=y CONFIG_SKY2=m # CONFIG_SKY2_DEBUG is not set CONFIG_NET_VENDOR_MELLANOX=y CONFIG_MLX4_EN=m CONFIG_MLX4_EN_DCB=y CONFIG_MLX4_CORE=m CONFIG_MLX4_DEBUG=y CONFIG_MLX4_CORE_GEN2=y CONFIG_MLX5_CORE=m # CONFIG_MLX5_FPGA is not set CONFIG_MLX5_CORE_EN=y CONFIG_MLX5_EN_ARFS=y CONFIG_MLX5_EN_RXNFC=y CONFIG_MLX5_MPFS=y CONFIG_MLX5_ESWITCH=y CONFIG_MLX5_CORE_EN_DCB=y CONFIG_MLX5_CORE_IPOIB=y CONFIG_MLXSW_CORE=m CONFIG_MLXSW_CORE_HWMON=y CONFIG_MLXSW_CORE_THERMAL=y CONFIG_MLXSW_PCI=m CONFIG_MLXSW_I2C=m CONFIG_MLXSW_SWITCHIB=m CONFIG_MLXSW_SWITCHX2=m CONFIG_MLXSW_SPECTRUM=m CONFIG_MLXSW_SPECTRUM_DCB=y CONFIG_MLXSW_MINIMAL=m CONFIG_MLXFW=m # CONFIG_NET_VENDOR_MICREL is not set # CONFIG_NET_VENDOR_MICROCHIP is not set CONFIG_NET_VENDOR_MICROSEMI=y # CONFIG_MSCC_OCELOT_SWITCH is not set CONFIG_NET_VENDOR_MYRI=y CONFIG_MYRI10GE=m CONFIG_MYRI10GE_DCA=y # CONFIG_FEALNX is not set # CONFIG_NET_VENDOR_NATSEMI is not set CONFIG_NET_VENDOR_NETERION=y # CONFIG_S2IO is not set # CONFIG_VXGE is not set CONFIG_NET_VENDOR_NETRONOME=y CONFIG_NFP=m CONFIG_NFP_APP_FLOWER=y CONFIG_NFP_APP_ABM_NIC=y # CONFIG_NFP_DEBUG is not set CONFIG_NET_VENDOR_NI=y # CONFIG_NI_XGE_MANAGEMENT_ENET is not set # CONFIG_NET_VENDOR_NVIDIA is not set CONFIG_NET_VENDOR_OKI=y CONFIG_ETHOC=m CONFIG_NET_VENDOR_PACKET_ENGINES=y # CONFIG_HAMACHI is not set CONFIG_YELLOWFIN=m CONFIG_NET_VENDOR_QLOGIC=y CONFIG_QLA3XXX=m CONFIG_QLCNIC=m CONFIG_QLCNIC_SRIOV=y CONFIG_QLCNIC_DCB=y CONFIG_QLCNIC_HWMON=y CONFIG_QLGE=m CONFIG_NETXEN_NIC=m CONFIG_QED=m CONFIG_QED_LL2=y CONFIG_QED_SRIOV=y CONFIG_QEDE=m CONFIG_QED_RDMA=y CONFIG_QED_ISCSI=y CONFIG_QED_FCOE=y CONFIG_QED_OOO=y CONFIG_NET_VENDOR_QUALCOMM=y # CONFIG_QCOM_EMAC is not set # CONFIG_RMNET is not set # CONFIG_NET_VENDOR_RDC is not set CONFIG_NET_VENDOR_REALTEK=y # CONFIG_ATP is not set CONFIG_8139CP=y CONFIG_8139TOO=y # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set CONFIG_R8169=y CONFIG_NET_VENDOR_RENESAS=y CONFIG_NET_VENDOR_ROCKER=y CONFIG_ROCKER=m CONFIG_NET_VENDOR_SAMSUNG=y # CONFIG_SXGBE_ETH is not set # CONFIG_NET_VENDOR_SEEQ is not set CONFIG_NET_VENDOR_SOLARFLARE=y CONFIG_SFC=m CONFIG_SFC_MTD=y CONFIG_SFC_MCDI_MON=y CONFIG_SFC_SRIOV=y CONFIG_SFC_MCDI_LOGGING=y CONFIG_SFC_FALCON=m CONFIG_SFC_FALCON_MTD=y # CONFIG_NET_VENDOR_SILAN is not set # CONFIG_NET_VENDOR_SIS is not set CONFIG_NET_VENDOR_SMSC=y CONFIG_EPIC100=m # CONFIG_SMSC911X is not set CONFIG_SMSC9420=m CONFIG_NET_VENDOR_SOCIONEXT=y # CONFIG_NET_VENDOR_STMICRO is not set # CONFIG_NET_VENDOR_SUN is not set CONFIG_NET_VENDOR_SYNOPSYS=y # CONFIG_DWC_XLGMAC is not set # CONFIG_NET_VENDOR_TEHUTI is not set CONFIG_NET_VENDOR_TI=y # CONFIG_TI_CPSW_PHY_SEL is not set # CONFIG_TI_CPSW_ALE is not set CONFIG_TLAN=m # CONFIG_NET_VENDOR_VIA is not set # CONFIG_NET_VENDOR_WIZNET is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_NET_SB1000 is not set CONFIG_MDIO_DEVICE=y CONFIG_MDIO_BUS=y # CONFIG_MDIO_BCM_UNIMAC is not set CONFIG_MDIO_BITBANG=m # CONFIG_MDIO_GPIO is not set # CONFIG_MDIO_MSCC_MIIM is not set # CONFIG_MDIO_THUNDER is not set CONFIG_PHYLIB=y CONFIG_SWPHY=y # CONFIG_LED_TRIGGER_PHY is not set # # MII PHY device drivers # CONFIG_AMD_PHY=m # CONFIG_AQUANTIA_PHY is not set # CONFIG_ASIX_PHY is not set CONFIG_AT803X_PHY=m # CONFIG_BCM7XXX_PHY is not set CONFIG_BCM87XX_PHY=m CONFIG_BCM_NET_PHYLIB=m CONFIG_BROADCOM_PHY=m CONFIG_CICADA_PHY=m # CONFIG_CORTINA_PHY is not set CONFIG_DAVICOM_PHY=m # CONFIG_DP83822_PHY is not set # CONFIG_DP83TC811_PHY is not set # CONFIG_DP83848_PHY is not set # CONFIG_DP83867_PHY is not set CONFIG_FIXED_PHY=y CONFIG_ICPLUS_PHY=m # CONFIG_INTEL_XWAY_PHY is not set CONFIG_LSI_ET1011C_PHY=m CONFIG_LXT_PHY=m CONFIG_MARVELL_PHY=m # CONFIG_MARVELL_10G_PHY is not set CONFIG_MICREL_PHY=m # CONFIG_MICROCHIP_PHY is not set # CONFIG_MICROCHIP_T1_PHY is not set # CONFIG_MICROSEMI_PHY is not set CONFIG_NATIONAL_PHY=m CONFIG_QSEMI_PHY=m CONFIG_REALTEK_PHY=y # CONFIG_RENESAS_PHY is not set # CONFIG_ROCKCHIP_PHY is not set CONFIG_SMSC_PHY=m CONFIG_STE10XP=m # CONFIG_TERANETICS_PHY is not set CONFIG_VITESSE_PHY=m # CONFIG_XILINX_GMII2RGMII is not set # CONFIG_MICREL_KS8995MA is not set # CONFIG_PLIP is not set CONFIG_PPP=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_FILTER=y CONFIG_PPP_MPPE=m CONFIG_PPP_MULTILINK=y CONFIG_PPPOATM=m CONFIG_PPPOE=m CONFIG_PPTP=m CONFIG_PPPOL2TP=m CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_SLIP=m CONFIG_SLHC=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLIP_SMART=y # CONFIG_SLIP_MODE_SLIP6 is not set CONFIG_USB_NET_DRIVERS=y CONFIG_USB_CATC=y CONFIG_USB_KAWETH=y CONFIG_USB_PEGASUS=y CONFIG_USB_RTL8150=y CONFIG_USB_RTL8152=m # CONFIG_USB_LAN78XX is not set CONFIG_USB_USBNET=y CONFIG_USB_NET_AX8817X=y CONFIG_USB_NET_AX88179_178A=m CONFIG_USB_NET_CDCETHER=y CONFIG_USB_NET_CDC_EEM=y CONFIG_USB_NET_CDC_NCM=m CONFIG_USB_NET_HUAWEI_CDC_NCM=m CONFIG_USB_NET_CDC_MBIM=m CONFIG_USB_NET_DM9601=y # CONFIG_USB_NET_SR9700 is not set # CONFIG_USB_NET_SR9800 is not set CONFIG_USB_NET_SMSC75XX=y CONFIG_USB_NET_SMSC95XX=y CONFIG_USB_NET_GL620A=y CONFIG_USB_NET_NET1080=y CONFIG_USB_NET_PLUSB=y CONFIG_USB_NET_MCS7830=y CONFIG_USB_NET_RNDIS_HOST=y CONFIG_USB_NET_CDC_SUBSET_ENABLE=y CONFIG_USB_NET_CDC_SUBSET=y CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=y CONFIG_USB_NET_CX82310_ETH=m CONFIG_USB_NET_KALMIA=m CONFIG_USB_NET_QMI_WWAN=m CONFIG_USB_HSO=m CONFIG_USB_NET_INT51X1=y CONFIG_USB_IPHETH=y CONFIG_USB_SIERRA_NET=y CONFIG_USB_VL600=m # CONFIG_USB_NET_CH9200 is not set # CONFIG_USB_NET_AQC111 is not set CONFIG_WLAN=y # CONFIG_WIRELESS_WDS is not set CONFIG_WLAN_VENDOR_ADMTEK=y # CONFIG_ADM8211 is not set CONFIG_ATH_COMMON=m CONFIG_WLAN_VENDOR_ATH=y # CONFIG_ATH_DEBUG is not set # CONFIG_ATH5K is not set # CONFIG_ATH5K_PCI is not set CONFIG_ATH9K_HW=m CONFIG_ATH9K_COMMON=m CONFIG_ATH9K_COMMON_DEBUG=y CONFIG_ATH9K_BTCOEX_SUPPORT=y CONFIG_ATH9K=m CONFIG_ATH9K_PCI=y CONFIG_ATH9K_AHB=y CONFIG_ATH9K_DEBUGFS=y # CONFIG_ATH9K_STATION_STATISTICS is not set # CONFIG_ATH9K_DYNACK is not set CONFIG_ATH9K_WOW=y CONFIG_ATH9K_RFKILL=y # CONFIG_ATH9K_CHANNEL_CONTEXT is not set CONFIG_ATH9K_PCOEM=y CONFIG_ATH9K_HTC=m # CONFIG_ATH9K_HTC_DEBUGFS is not set # CONFIG_ATH9K_HWRNG is not set # CONFIG_ATH9K_COMMON_SPECTRAL is not set CONFIG_CARL9170=m CONFIG_CARL9170_LEDS=y # CONFIG_CARL9170_DEBUGFS is not set CONFIG_CARL9170_WPC=y # CONFIG_CARL9170_HWRNG is not set # CONFIG_ATH6KL is not set # CONFIG_AR5523 is not set CONFIG_WIL6210=m CONFIG_WIL6210_ISR_COR=y CONFIG_WIL6210_TRACING=y CONFIG_WIL6210_DEBUGFS=y CONFIG_ATH10K=m CONFIG_ATH10K_CE=y CONFIG_ATH10K_PCI=m # CONFIG_ATH10K_SDIO is not set # CONFIG_ATH10K_USB is not set # CONFIG_ATH10K_DEBUG is not set CONFIG_ATH10K_DEBUGFS=y # CONFIG_ATH10K_SPECTRAL is not set # CONFIG_ATH10K_TRACING is not set # CONFIG_WCN36XX is not set CONFIG_WLAN_VENDOR_ATMEL=y # CONFIG_ATMEL is not set # CONFIG_AT76C50X_USB is not set CONFIG_WLAN_VENDOR_BROADCOM=y # CONFIG_B43 is not set # CONFIG_B43LEGACY is not set CONFIG_BRCMUTIL=m CONFIG_BRCMSMAC=m CONFIG_BRCMFMAC=m CONFIG_BRCMFMAC_PROTO_BCDC=y CONFIG_BRCMFMAC_PROTO_MSGBUF=y CONFIG_BRCMFMAC_SDIO=y CONFIG_BRCMFMAC_USB=y CONFIG_BRCMFMAC_PCIE=y # CONFIG_BRCM_TRACING is not set # CONFIG_BRCMDBG is not set CONFIG_WLAN_VENDOR_CISCO=y # CONFIG_AIRO is not set CONFIG_WLAN_VENDOR_INTEL=y # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set CONFIG_IWLEGACY=m CONFIG_IWL4965=m CONFIG_IWL3945=m # # iwl3945 / iwl4965 Debugging Options # CONFIG_IWLEGACY_DEBUG=y CONFIG_IWLEGACY_DEBUGFS=y CONFIG_IWLWIFI=m CONFIG_IWLWIFI_LEDS=y CONFIG_IWLDVM=m CONFIG_IWLMVM=m CONFIG_IWLWIFI_OPMODE_MODULAR=y # CONFIG_IWLWIFI_BCAST_FILTERING is not set # CONFIG_IWLWIFI_PCIE_RTPM is not set # # Debugging Options # # CONFIG_IWLWIFI_DEBUG is not set CONFIG_IWLWIFI_DEBUGFS=y # CONFIG_IWLWIFI_DEVICE_TRACING is not set CONFIG_WLAN_VENDOR_INTERSIL=y # CONFIG_HOSTAP is not set # CONFIG_HERMES is not set # CONFIG_P54_COMMON is not set # CONFIG_PRISM54 is not set CONFIG_WLAN_VENDOR_MARVELL=y # CONFIG_LIBERTAS is not set # CONFIG_LIBERTAS_THINFIRM is not set CONFIG_MWIFIEX=m CONFIG_MWIFIEX_SDIO=m CONFIG_MWIFIEX_PCIE=m CONFIG_MWIFIEX_USB=m CONFIG_MWL8K=m CONFIG_WLAN_VENDOR_MEDIATEK=y # CONFIG_MT7601U is not set # CONFIG_MT76x0U is not set # CONFIG_MT76x0E is not set # CONFIG_MT76x2E is not set # CONFIG_MT76x2U is not set # CONFIG_MT7603E is not set CONFIG_WLAN_VENDOR_RALINK=y CONFIG_RT2X00=m # CONFIG_RT2400PCI is not set # CONFIG_RT2500PCI is not set CONFIG_RT61PCI=m CONFIG_RT2800PCI=m CONFIG_RT2800PCI_RT33XX=y CONFIG_RT2800PCI_RT35XX=y CONFIG_RT2800PCI_RT53XX=y CONFIG_RT2800PCI_RT3290=y # CONFIG_RT2500USB is not set CONFIG_RT73USB=m CONFIG_RT2800USB=m CONFIG_RT2800USB_RT33XX=y CONFIG_RT2800USB_RT35XX=y CONFIG_RT2800USB_RT3573=y CONFIG_RT2800USB_RT53XX=y CONFIG_RT2800USB_RT55XX=y CONFIG_RT2800USB_UNKNOWN=y CONFIG_RT2800_LIB=m CONFIG_RT2800_LIB_MMIO=m CONFIG_RT2X00_LIB_MMIO=m CONFIG_RT2X00_LIB_PCI=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_CRYPTO=y CONFIG_RT2X00_LIB_LEDS=y CONFIG_RT2X00_LIB_DEBUGFS=y # CONFIG_RT2X00_DEBUG is not set CONFIG_WLAN_VENDOR_REALTEK=y # CONFIG_RTL8180 is not set CONFIG_RTL8187=m CONFIG_RTL8187_LEDS=y CONFIG_RTL_CARDS=m CONFIG_RTL8192CE=m CONFIG_RTL8192SE=m CONFIG_RTL8192DE=m CONFIG_RTL8723AE=m CONFIG_RTL8723BE=m CONFIG_RTL8188EE=m CONFIG_RTL8192EE=m CONFIG_RTL8821AE=m CONFIG_RTL8192CU=m CONFIG_RTLWIFI=m CONFIG_RTLWIFI_PCI=m CONFIG_RTLWIFI_USB=m # CONFIG_RTLWIFI_DEBUG is not set CONFIG_RTL8192C_COMMON=m CONFIG_RTL8723_COMMON=m CONFIG_RTLBTCOEXIST=m # CONFIG_RTL8XXXU is not set CONFIG_WLAN_VENDOR_RSI=y # CONFIG_RSI_91X is not set CONFIG_WLAN_VENDOR_ST=y # CONFIG_CW1200 is not set CONFIG_WLAN_VENDOR_TI=y # CONFIG_WL1251 is not set # CONFIG_WL12XX is not set # CONFIG_WL18XX is not set # CONFIG_WLCORE is not set CONFIG_WLAN_VENDOR_ZYDAS=y # CONFIG_USB_ZD1201 is not set # CONFIG_ZD1211RW is not set CONFIG_WLAN_VENDOR_QUANTENNA=y # CONFIG_QTNFMAC_PCIE is not set CONFIG_MAC80211_HWSIM=m # CONFIG_USB_NET_RNDIS_WLAN is not set # CONFIG_VIRT_WIFI is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # CONFIG_WAN=y # CONFIG_LANMEDIA is not set CONFIG_HDLC=m CONFIG_HDLC_RAW=m # CONFIG_HDLC_RAW_ETH is not set CONFIG_HDLC_CISCO=m CONFIG_HDLC_FR=m CONFIG_HDLC_PPP=m # # X.25/LAPB support is disabled # # CONFIG_PCI200SYN is not set # CONFIG_WANXL is not set # CONFIG_PC300TOO is not set # CONFIG_FARSYNC is not set # CONFIG_DSCC4 is not set CONFIG_DLCI=m CONFIG_DLCI_MAX=8 # CONFIG_SBNI is not set CONFIG_IEEE802154_DRIVERS=m CONFIG_IEEE802154_FAKELB=m # CONFIG_IEEE802154_AT86RF230 is not set # CONFIG_IEEE802154_MRF24J40 is not set # CONFIG_IEEE802154_CC2520 is not set # CONFIG_IEEE802154_ATUSB is not set # CONFIG_IEEE802154_ADF7242 is not set # CONFIG_IEEE802154_CA8210 is not set # CONFIG_IEEE802154_MCR20A is not set # CONFIG_IEEE802154_HWSIM is not set CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_VMXNET3=m CONFIG_FUJITSU_ES=m CONFIG_THUNDERBOLT_NET=m CONFIG_HYPERV_NET=m CONFIG_NETDEVSIM=m CONFIG_NET_FAILOVER=m CONFIG_ISDN=y CONFIG_ISDN_I4L=m CONFIG_ISDN_PPP=y CONFIG_ISDN_PPP_VJ=y CONFIG_ISDN_MPP=y CONFIG_IPPP_FILTER=y # CONFIG_ISDN_PPP_BSDCOMP is not set CONFIG_ISDN_AUDIO=y CONFIG_ISDN_TTY_FAX=y # # ISDN feature submodules # CONFIG_ISDN_DIVERSION=m # # ISDN4Linux hardware drivers # # # Passive cards # CONFIG_ISDN_DRV_HISAX=m # # D-channel protocol features # CONFIG_HISAX_EURO=y CONFIG_DE_AOC=y CONFIG_HISAX_NO_SENDCOMPLETE=y CONFIG_HISAX_NO_LLC=y CONFIG_HISAX_NO_KEYPAD=y CONFIG_HISAX_1TR6=y CONFIG_HISAX_NI1=y CONFIG_HISAX_MAX_CARDS=8 # # HiSax supported cards # CONFIG_HISAX_16_3=y CONFIG_HISAX_TELESPCI=y CONFIG_HISAX_S0BOX=y CONFIG_HISAX_FRITZPCI=y CONFIG_HISAX_AVM_A1_PCMCIA=y CONFIG_HISAX_ELSA=y CONFIG_HISAX_DIEHLDIVA=y CONFIG_HISAX_SEDLBAUER=y CONFIG_HISAX_NETJET=y CONFIG_HISAX_NETJET_U=y CONFIG_HISAX_NICCY=y CONFIG_HISAX_BKM_A4T=y CONFIG_HISAX_SCT_QUADRO=y CONFIG_HISAX_GAZEL=y CONFIG_HISAX_HFC_PCI=y CONFIG_HISAX_W6692=y CONFIG_HISAX_HFC_SX=y CONFIG_HISAX_ENTERNOW_PCI=y # CONFIG_HISAX_DEBUG is not set # # HiSax PCMCIA card service modules # # # HiSax sub driver modules # CONFIG_HISAX_ST5481=m # CONFIG_HISAX_HFCUSB is not set CONFIG_HISAX_HFC4S8S=m CONFIG_HISAX_FRITZ_PCIPNP=m CONFIG_ISDN_CAPI=m # CONFIG_CAPI_TRACE is not set CONFIG_ISDN_CAPI_CAPI20=m CONFIG_ISDN_CAPI_MIDDLEWARE=y CONFIG_ISDN_CAPI_CAPIDRV=m # CONFIG_ISDN_CAPI_CAPIDRV_VERBOSE is not set # # CAPI hardware drivers # CONFIG_CAPI_AVM=y CONFIG_ISDN_DRV_AVMB1_B1PCI=m CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y CONFIG_ISDN_DRV_AVMB1_T1PCI=m CONFIG_ISDN_DRV_AVMB1_C4=m CONFIG_ISDN_DRV_GIGASET=m CONFIG_GIGASET_CAPI=y CONFIG_GIGASET_BASE=m CONFIG_GIGASET_M105=m CONFIG_GIGASET_M101=m # CONFIG_GIGASET_DEBUG is not set CONFIG_HYSDN=m CONFIG_HYSDN_CAPI=y CONFIG_MISDN=m CONFIG_MISDN_DSP=m CONFIG_MISDN_L1OIP=m # # mISDN hardware drivers # CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCUSB=m CONFIG_MISDN_AVMFRITZ=m CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_INFINEON=m CONFIG_MISDN_W6692=m CONFIG_MISDN_NETJET=m CONFIG_MISDN_IPAC=m CONFIG_MISDN_ISAR=m CONFIG_ISDN_HDLC=m # CONFIG_NVM is not set # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_LEDS=y CONFIG_INPUT_FF_MEMLESS=y CONFIG_INPUT_POLLDEV=m CONFIG_INPUT_SPARSEKMAP=m # CONFIG_INPUT_MATRIXKMAP is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y # CONFIG_INPUT_MOUSEDEV_PSAUX is not set CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ADC is not set # CONFIG_KEYBOARD_ADP5588 is not set # CONFIG_KEYBOARD_ADP5589 is not set CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_QT1070 is not set # CONFIG_KEYBOARD_QT2160 is not set # CONFIG_KEYBOARD_DLINK_DIR685 is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_GPIO is not set # CONFIG_KEYBOARD_GPIO_POLLED is not set # CONFIG_KEYBOARD_TCA6416 is not set # CONFIG_KEYBOARD_TCA8418 is not set # CONFIG_KEYBOARD_MATRIX is not set # CONFIG_KEYBOARD_LM8323 is not set # CONFIG_KEYBOARD_LM8333 is not set # CONFIG_KEYBOARD_MAX7359 is not set # CONFIG_KEYBOARD_MCS is not set # CONFIG_KEYBOARD_MPR121 is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_OPENCORES is not set # CONFIG_KEYBOARD_SAMSUNG is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_TM2_TOUCHKEY is not set # CONFIG_KEYBOARD_XTKBD is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_BYD=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y CONFIG_MOUSE_PS2_CYPRESS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y CONFIG_MOUSE_PS2_ELANTECH=y CONFIG_MOUSE_PS2_ELANTECH_SMBUS=y CONFIG_MOUSE_PS2_SENTELIC=y # CONFIG_MOUSE_PS2_TOUCHKIT is not set CONFIG_MOUSE_PS2_FOCALTECH=y CONFIG_MOUSE_PS2_VMMOUSE=y CONFIG_MOUSE_PS2_SMBUS=y CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m CONFIG_MOUSE_CYAPA=m # CONFIG_MOUSE_ELAN_I2C is not set CONFIG_MOUSE_VSXXXAA=m # CONFIG_MOUSE_GPIO is not set CONFIG_MOUSE_SYNAPTICS_I2C=m CONFIG_MOUSE_SYNAPTICS_USB=m # CONFIG_INPUT_JOYSTICK is not set CONFIG_INPUT_TABLET=y CONFIG_TABLET_USB_ACECAD=m CONFIG_TABLET_USB_AIPTEK=m CONFIG_TABLET_USB_GTCO=m # CONFIG_TABLET_USB_HANWANG is not set CONFIG_TABLET_USB_KBTAB=m # CONFIG_TABLET_USB_PEGASUS is not set # CONFIG_TABLET_SERIAL_WACOM4 is not set CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_PROPERTIES=y # CONFIG_TOUCHSCREEN_ADS7846 is not set # CONFIG_TOUCHSCREEN_AD7877 is not set # CONFIG_TOUCHSCREEN_AD7879 is not set # CONFIG_TOUCHSCREEN_ADC is not set # CONFIG_TOUCHSCREEN_ATMEL_MXT is not set # CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set # CONFIG_TOUCHSCREEN_BU21013 is not set # CONFIG_TOUCHSCREEN_BU21029 is not set # CONFIG_TOUCHSCREEN_CHIPONE_ICN8505 is not set # CONFIG_TOUCHSCREEN_CY8CTMG110 is not set # CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set # CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set # CONFIG_TOUCHSCREEN_DYNAPRO is not set # CONFIG_TOUCHSCREEN_HAMPSHIRE is not set # CONFIG_TOUCHSCREEN_EETI is not set # CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set # CONFIG_TOUCHSCREEN_EXC3000 is not set # CONFIG_TOUCHSCREEN_FUJITSU is not set # CONFIG_TOUCHSCREEN_GOODIX is not set # CONFIG_TOUCHSCREEN_HIDEEP is not set # CONFIG_TOUCHSCREEN_ILI210X is not set # CONFIG_TOUCHSCREEN_S6SY761 is not set # CONFIG_TOUCHSCREEN_GUNZE is not set # CONFIG_TOUCHSCREEN_EKTF2127 is not set # CONFIG_TOUCHSCREEN_ELAN is not set CONFIG_TOUCHSCREEN_ELO=m CONFIG_TOUCHSCREEN_WACOM_W8001=m CONFIG_TOUCHSCREEN_WACOM_I2C=m # CONFIG_TOUCHSCREEN_MAX11801 is not set # CONFIG_TOUCHSCREEN_MCS5000 is not set # CONFIG_TOUCHSCREEN_MMS114 is not set # CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set # CONFIG_TOUCHSCREEN_MTOUCH is not set # CONFIG_TOUCHSCREEN_INEXIO is not set # CONFIG_TOUCHSCREEN_MK712 is not set # CONFIG_TOUCHSCREEN_PENMOUNT is not set # CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set # CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set # CONFIG_TOUCHSCREEN_TOUCHWIN is not set # CONFIG_TOUCHSCREEN_PIXCIR is not set # CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set # CONFIG_TOUCHSCREEN_WM97XX is not set # CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set # CONFIG_TOUCHSCREEN_TOUCHIT213 is not set # CONFIG_TOUCHSCREEN_TSC_SERIO is not set # CONFIG_TOUCHSCREEN_TSC2004 is not set # CONFIG_TOUCHSCREEN_TSC2005 is not set # CONFIG_TOUCHSCREEN_TSC2007 is not set # CONFIG_TOUCHSCREEN_RM_TS is not set # CONFIG_TOUCHSCREEN_SILEAD is not set # CONFIG_TOUCHSCREEN_SIS_I2C is not set # CONFIG_TOUCHSCREEN_ST1232 is not set # CONFIG_TOUCHSCREEN_STMFTS is not set # CONFIG_TOUCHSCREEN_SUR40 is not set # CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set # CONFIG_TOUCHSCREEN_SX8654 is not set # CONFIG_TOUCHSCREEN_TPS6507X is not set # CONFIG_TOUCHSCREEN_ZET6223 is not set # CONFIG_TOUCHSCREEN_ZFORCE is not set # CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set CONFIG_INPUT_MISC=y # CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_BMA150 is not set # CONFIG_INPUT_E3X0_BUTTON is not set # CONFIG_INPUT_MSM_VIBRATOR is not set CONFIG_INPUT_PCSPKR=m # CONFIG_INPUT_MMA8450 is not set CONFIG_INPUT_APANEL=m CONFIG_INPUT_GP2A=m # CONFIG_INPUT_GPIO_BEEPER is not set # CONFIG_INPUT_GPIO_DECODER is not set CONFIG_INPUT_ATLAS_BTNS=m CONFIG_INPUT_ATI_REMOTE2=m CONFIG_INPUT_KEYSPAN_REMOTE=m # CONFIG_INPUT_KXTJ9 is not set CONFIG_INPUT_POWERMATE=m CONFIG_INPUT_YEALINK=m CONFIG_INPUT_CM109=m CONFIG_INPUT_UINPUT=m # CONFIG_INPUT_PCF8574 is not set # CONFIG_INPUT_PWM_BEEPER is not set # CONFIG_INPUT_PWM_VIBRA is not set CONFIG_INPUT_GPIO_ROTARY_ENCODER=m # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_IMS_PCU is not set # CONFIG_INPUT_CMA3000 is not set CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m # CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set # CONFIG_INPUT_DRV260X_HAPTICS is not set # CONFIG_INPUT_DRV2665_HAPTICS is not set # CONFIG_INPUT_DRV2667_HAPTICS is not set CONFIG_RMI4_CORE=m # CONFIG_RMI4_I2C is not set # CONFIG_RMI4_SPI is not set CONFIG_RMI4_SMB=m CONFIG_RMI4_F03=y CONFIG_RMI4_F03_SERIO=m CONFIG_RMI4_2D_SENSOR=y CONFIG_RMI4_F11=y CONFIG_RMI4_F12=y CONFIG_RMI4_F30=y # CONFIG_RMI4_F34 is not set # CONFIG_RMI4_F54 is not set # CONFIG_RMI4_F55 is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=m CONFIG_SERIO_ALTERA_PS2=m # CONFIG_SERIO_PS2MULT is not set CONFIG_SERIO_ARC_PS2=m # CONFIG_SERIO_OLPC_APSP is not set CONFIG_HYPERV_KEYBOARD=m # CONFIG_SERIO_GPIO_PS2 is not set # CONFIG_USERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_TTY=y CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_VT_CONSOLE_SLEEP=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set CONFIG_SERIAL_NONSTANDARD=y # CONFIG_ROCKETPORT is not set CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set # CONFIG_MOXA_INTELLIO is not set # CONFIG_MOXA_SMARTIO is not set CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_SYNCLINK_GT=m CONFIG_NOZOMI=m # CONFIG_ISI is not set CONFIG_N_HDLC=m CONFIG_N_GSM=m # CONFIG_TRACE_SINK is not set CONFIG_LDISC_AUTOLOAD=y CONFIG_DEVMEM=y # CONFIG_DEVKMEM is not set # # Serial drivers # CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y # CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y # CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y # CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DW=y # CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y # CONFIG_SERIAL_8250_MOXA is not set # # Non-8250 serial port support # # CONFIG_SERIAL_MAX3100 is not set # CONFIG_SERIAL_MAX310X is not set # CONFIG_SERIAL_UARTLITE is not set CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_SERIAL_JSM=m # CONFIG_SERIAL_SCCNXP is not set # CONFIG_SERIAL_SC16IS7XX is not set # CONFIG_SERIAL_ALTERA_JTAGUART is not set # CONFIG_SERIAL_ALTERA_UART is not set # CONFIG_SERIAL_IFX6X60 is not set CONFIG_SERIAL_ARC=m CONFIG_SERIAL_ARC_NR_PORTS=1 # CONFIG_SERIAL_RP2 is not set # CONFIG_SERIAL_FSL_LPUART is not set # CONFIG_SERIAL_DEV_BUS is not set # CONFIG_TTY_PRINTK is not set CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y CONFIG_VIRTIO_CONSOLE=y CONFIG_IPMI_HANDLER=m CONFIG_IPMI_DMI_DECODE=y CONFIG_IPMI_PLAT_DATA=y # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_SSIF=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_TIMERIOMEM=m CONFIG_HW_RANDOM_INTEL=m CONFIG_HW_RANDOM_AMD=m CONFIG_HW_RANDOM_VIA=m CONFIG_HW_RANDOM_VIRTIO=y CONFIG_NVRAM=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_MWAVE is not set CONFIG_RAW_DRIVER=y CONFIG_MAX_RAW_DEVS=8192 CONFIG_HPET=y CONFIG_HPET_MMAP=y # CONFIG_HPET_MMAP_DEFAULT is not set CONFIG_HANGCHECK_TIMER=m CONFIG_UV_MMTIMER=m CONFIG_TCG_TPM=y CONFIG_HW_RANDOM_TPM=y CONFIG_TCG_TIS_CORE=y CONFIG_TCG_TIS=y # CONFIG_TCG_TIS_SPI is not set CONFIG_TCG_TIS_I2C_ATMEL=m CONFIG_TCG_TIS_I2C_INFINEON=m CONFIG_TCG_TIS_I2C_NUVOTON=m CONFIG_TCG_NSC=m CONFIG_TCG_ATMEL=m CONFIG_TCG_INFINEON=m # CONFIG_TCG_XEN is not set CONFIG_TCG_CRB=y # CONFIG_TCG_VTPM_PROXY is not set CONFIG_TCG_TIS_ST33ZP24=m CONFIG_TCG_TIS_ST33ZP24_I2C=m # CONFIG_TCG_TIS_ST33ZP24_SPI is not set CONFIG_TELCLOCK=m CONFIG_DEVPORT=y # CONFIG_XILLYBUS is not set # CONFIG_RANDOM_TRUST_CPU is not set # # I2C support # CONFIG_I2C=y CONFIG_ACPI_I2C_OPREGION=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=m CONFIG_I2C_MUX=m # # Multiplexer I2C Chip support # # CONFIG_I2C_MUX_GPIO is not set # CONFIG_I2C_MUX_LTC4306 is not set # CONFIG_I2C_MUX_PCA9541 is not set # CONFIG_I2C_MUX_PCA954x is not set # CONFIG_I2C_MUX_REG is not set # CONFIG_I2C_MUX_MLXCPLD is not set CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_SMBUS=m CONFIG_I2C_ALGOBIT=y CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set CONFIG_I2C_AMD756=m CONFIG_I2C_AMD756_S4882=m CONFIG_I2C_AMD8111=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_ISMT=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NFORCE2_S4985=m # CONFIG_I2C_NVIDIA_GPU is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m # # ACPI drivers # CONFIG_I2C_SCMI=m # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m CONFIG_I2C_DESIGNWARE_PLATFORM=m # CONFIG_I2C_DESIGNWARE_SLAVE is not set # CONFIG_I2C_DESIGNWARE_PCI is not set # CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set # CONFIG_I2C_EMEV2 is not set # CONFIG_I2C_GPIO is not set # CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_SIMTEC=m # CONFIG_I2C_XILINX is not set # # External I2C/SMBus adapter drivers # CONFIG_I2C_DIOLAN_U2C=m CONFIG_I2C_PARPORT=m CONFIG_I2C_PARPORT_LIGHT=m # CONFIG_I2C_ROBOTFUZZ_OSIF is not set # CONFIG_I2C_TAOS_EVM is not set CONFIG_I2C_TINY_USB=m CONFIG_I2C_VIPERBOARD=m # # Other I2C/SMBus bus drivers # # CONFIG_I2C_MLXCPLD is not set CONFIG_I2C_STUB=m # CONFIG_I2C_SLAVE is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I3C is not set CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y # CONFIG_SPI_MEM is not set # # SPI Master Controller Drivers # # CONFIG_SPI_ALTERA is not set # CONFIG_SPI_AXI_SPI_ENGINE is not set # CONFIG_SPI_BITBANG is not set # CONFIG_SPI_BUTTERFLY is not set # CONFIG_SPI_CADENCE is not set # CONFIG_SPI_DESIGNWARE is not set # CONFIG_SPI_NXP_FLEXSPI is not set # CONFIG_SPI_GPIO is not set # CONFIG_SPI_LM70_LLP is not set # CONFIG_SPI_OC_TINY is not set # CONFIG_SPI_PXA2XX is not set # CONFIG_SPI_ROCKCHIP is not set # CONFIG_SPI_SC18IS602 is not set # CONFIG_SPI_SIFIVE is not set # CONFIG_SPI_MXIC is not set # CONFIG_SPI_XCOMM is not set # CONFIG_SPI_XILINX is not set # CONFIG_SPI_ZYNQMP_GQSPI is not set # # SPI Protocol Masters # # CONFIG_SPI_SPIDEV is not set # CONFIG_SPI_LOOPBACK_TEST is not set # CONFIG_SPI_TLE62X0 is not set # CONFIG_SPI_SLAVE is not set # CONFIG_SPMI is not set # CONFIG_HSI is not set CONFIG_PPS=y # CONFIG_PPS_DEBUG is not set # # PPS clients support # # CONFIG_PPS_CLIENT_KTIMER is not set CONFIG_PPS_CLIENT_LDISC=m CONFIG_PPS_CLIENT_PARPORT=m CONFIG_PPS_CLIENT_GPIO=m # # PPS generators support # # # PTP clock support # CONFIG_PTP_1588_CLOCK=y CONFIG_DP83640_PHY=m CONFIG_PTP_1588_CLOCK_KVM=m CONFIG_PINCTRL=y CONFIG_PINMUX=y CONFIG_PINCONF=y CONFIG_GENERIC_PINCONF=y # CONFIG_DEBUG_PINCTRL is not set CONFIG_PINCTRL_AMD=m # CONFIG_PINCTRL_MCP23S08 is not set # CONFIG_PINCTRL_SX150X is not set CONFIG_PINCTRL_BAYTRAIL=y # CONFIG_PINCTRL_CHERRYVIEW is not set CONFIG_PINCTRL_INTEL=m # CONFIG_PINCTRL_BROXTON is not set CONFIG_PINCTRL_CANNONLAKE=m # CONFIG_PINCTRL_CEDARFORK is not set CONFIG_PINCTRL_DENVERTON=m CONFIG_PINCTRL_GEMINILAKE=m # CONFIG_PINCTRL_ICELAKE is not set CONFIG_PINCTRL_LEWISBURG=m CONFIG_PINCTRL_SUNRISEPOINT=m CONFIG_GPIOLIB=y CONFIG_GPIOLIB_FASTPATH_LIMIT=512 CONFIG_GPIO_ACPI=y CONFIG_GPIOLIB_IRQCHIP=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y CONFIG_GPIO_GENERIC=m # # Memory mapped GPIO drivers # CONFIG_GPIO_AMDPT=m # CONFIG_GPIO_DWAPB is not set # CONFIG_GPIO_EXAR is not set # CONFIG_GPIO_GENERIC_PLATFORM is not set CONFIG_GPIO_ICH=m # CONFIG_GPIO_LYNXPOINT is not set # CONFIG_GPIO_MB86S7X is not set CONFIG_GPIO_MOCKUP=y # CONFIG_GPIO_VX855 is not set # CONFIG_GPIO_AMD_FCH is not set # # Port-mapped I/O GPIO drivers # # CONFIG_GPIO_F7188X is not set # CONFIG_GPIO_IT87 is not set # CONFIG_GPIO_SCH is not set # CONFIG_GPIO_SCH311X is not set # CONFIG_GPIO_WINBOND is not set # CONFIG_GPIO_WS16C48 is not set # # I2C GPIO expanders # # CONFIG_GPIO_ADP5588 is not set # CONFIG_GPIO_MAX7300 is not set # CONFIG_GPIO_MAX732X is not set # CONFIG_GPIO_PCA953X is not set # CONFIG_GPIO_PCF857X is not set # CONFIG_GPIO_TPIC2810 is not set # # MFD GPIO expanders # # # PCI GPIO expanders # # CONFIG_GPIO_AMD8111 is not set # CONFIG_GPIO_ML_IOH is not set # CONFIG_GPIO_PCI_IDIO_16 is not set # CONFIG_GPIO_PCIE_IDIO_24 is not set # CONFIG_GPIO_RDC321X is not set # # SPI GPIO expanders # # CONFIG_GPIO_MAX3191X is not set # CONFIG_GPIO_MAX7301 is not set # CONFIG_GPIO_MC33880 is not set # CONFIG_GPIO_PISOSR is not set # CONFIG_GPIO_XRA1403 is not set # # USB GPIO expanders # CONFIG_GPIO_VIPERBOARD=m # CONFIG_W1 is not set # CONFIG_POWER_AVS is not set CONFIG_POWER_RESET=y # CONFIG_POWER_RESET_RESTART is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_GENERIC_ADC_BATTERY is not set # CONFIG_TEST_POWER is not set # CONFIG_CHARGER_ADP5061 is not set # CONFIG_BATTERY_DS2780 is not set # CONFIG_BATTERY_DS2781 is not set # CONFIG_BATTERY_DS2782 is not set # CONFIG_BATTERY_SBS is not set # CONFIG_CHARGER_SBS is not set # CONFIG_MANAGER_SBS is not set # CONFIG_BATTERY_BQ27XXX is not set # CONFIG_BATTERY_MAX17040 is not set # CONFIG_BATTERY_MAX17042 is not set # CONFIG_CHARGER_MAX8903 is not set # CONFIG_CHARGER_LP8727 is not set # CONFIG_CHARGER_GPIO is not set # CONFIG_CHARGER_LTC3651 is not set # CONFIG_CHARGER_BQ2415X is not set # CONFIG_CHARGER_BQ24257 is not set # CONFIG_CHARGER_BQ24735 is not set # CONFIG_CHARGER_BQ25890 is not set CONFIG_CHARGER_SMB347=m # CONFIG_BATTERY_GAUGE_LTC2941 is not set # CONFIG_CHARGER_RT9455 is not set CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # CONFIG_SENSORS_ABITUGURU=m CONFIG_SENSORS_ABITUGURU3=m # CONFIG_SENSORS_AD7314 is not set CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m CONFIG_SENSORS_ADM1021=m CONFIG_SENSORS_ADM1025=m CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7X10=m # CONFIG_SENSORS_ADT7310 is not set CONFIG_SENSORS_ADT7410=m CONFIG_SENSORS_ADT7411=m CONFIG_SENSORS_ADT7462=m CONFIG_SENSORS_ADT7470=m CONFIG_SENSORS_ADT7475=m CONFIG_SENSORS_ASC7621=m CONFIG_SENSORS_K8TEMP=m CONFIG_SENSORS_K10TEMP=m CONFIG_SENSORS_FAM15H_POWER=m CONFIG_SENSORS_APPLESMC=m CONFIG_SENSORS_ASB100=m # CONFIG_SENSORS_ASPEED is not set CONFIG_SENSORS_ATXP1=m CONFIG_SENSORS_DS620=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_DELL_SMM=m CONFIG_SENSORS_I5K_AMB=m CONFIG_SENSORS_F71805F=m CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m CONFIG_SENSORS_FSCHMD=m # CONFIG_SENSORS_FTSTEUTATES is not set CONFIG_SENSORS_GL518SM=m CONFIG_SENSORS_GL520SM=m CONFIG_SENSORS_G760A=m # CONFIG_SENSORS_G762 is not set # CONFIG_SENSORS_HIH6130 is not set CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m # CONFIG_SENSORS_IIO_HWMON is not set # CONFIG_SENSORS_I5500 is not set CONFIG_SENSORS_CORETEMP=m CONFIG_SENSORS_IT87=m CONFIG_SENSORS_JC42=m # CONFIG_SENSORS_POWR1220 is not set CONFIG_SENSORS_LINEAGE=m # CONFIG_SENSORS_LTC2945 is not set # CONFIG_SENSORS_LTC2990 is not set CONFIG_SENSORS_LTC4151=m CONFIG_SENSORS_LTC4215=m # CONFIG_SENSORS_LTC4222 is not set CONFIG_SENSORS_LTC4245=m # CONFIG_SENSORS_LTC4260 is not set CONFIG_SENSORS_LTC4261=m # CONFIG_SENSORS_MAX1111 is not set CONFIG_SENSORS_MAX16065=m CONFIG_SENSORS_MAX1619=m CONFIG_SENSORS_MAX1668=m CONFIG_SENSORS_MAX197=m # CONFIG_SENSORS_MAX31722 is not set # CONFIG_SENSORS_MAX6621 is not set CONFIG_SENSORS_MAX6639=m CONFIG_SENSORS_MAX6642=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_MAX6697=m # CONFIG_SENSORS_MAX31790 is not set CONFIG_SENSORS_MCP3021=m # CONFIG_SENSORS_TC654 is not set # CONFIG_SENSORS_ADCXX is not set CONFIG_SENSORS_LM63=m # CONFIG_SENSORS_LM70 is not set CONFIG_SENSORS_LM73=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m CONFIG_SENSORS_LM95234=m CONFIG_SENSORS_LM95241=m CONFIG_SENSORS_LM95245=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_NTC_THERMISTOR=m # CONFIG_SENSORS_NCT6683 is not set CONFIG_SENSORS_NCT6775=m # CONFIG_SENSORS_NCT7802 is not set # CONFIG_SENSORS_NCT7904 is not set # CONFIG_SENSORS_NPCM7XX is not set # CONFIG_SENSORS_OCC_P8_I2C is not set CONFIG_SENSORS_PCF8591=m CONFIG_PMBUS=m CONFIG_SENSORS_PMBUS=m CONFIG_SENSORS_ADM1275=m # CONFIG_SENSORS_IBM_CFFPS is not set # CONFIG_SENSORS_IR35221 is not set CONFIG_SENSORS_LM25066=m CONFIG_SENSORS_LTC2978=m # CONFIG_SENSORS_LTC3815 is not set CONFIG_SENSORS_MAX16064=m # CONFIG_SENSORS_MAX20751 is not set # CONFIG_SENSORS_MAX31785 is not set CONFIG_SENSORS_MAX34440=m CONFIG_SENSORS_MAX8688=m # CONFIG_SENSORS_TPS40422 is not set # CONFIG_SENSORS_TPS53679 is not set CONFIG_SENSORS_UCD9000=m CONFIG_SENSORS_UCD9200=m CONFIG_SENSORS_ZL6100=m CONFIG_SENSORS_SHT15=m CONFIG_SENSORS_SHT21=m # CONFIG_SENSORS_SHT3x is not set # CONFIG_SENSORS_SHTC1 is not set CONFIG_SENSORS_SIS5595=m CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_EMC1403=m # CONFIG_SENSORS_EMC2103 is not set CONFIG_SENSORS_EMC6W201=m CONFIG_SENSORS_SMSC47M1=m CONFIG_SENSORS_SMSC47M192=m CONFIG_SENSORS_SMSC47B397=m CONFIG_SENSORS_SCH56XX_COMMON=m CONFIG_SENSORS_SCH5627=m CONFIG_SENSORS_SCH5636=m # CONFIG_SENSORS_STTS751 is not set # CONFIG_SENSORS_SMM665 is not set # CONFIG_SENSORS_ADC128D818 is not set CONFIG_SENSORS_ADS1015=m CONFIG_SENSORS_ADS7828=m # CONFIG_SENSORS_ADS7871 is not set CONFIG_SENSORS_AMC6821=m CONFIG_SENSORS_INA209=m CONFIG_SENSORS_INA2XX=m # CONFIG_SENSORS_INA3221 is not set # CONFIG_SENSORS_TC74 is not set CONFIG_SENSORS_THMC50=m CONFIG_SENSORS_TMP102=m # CONFIG_SENSORS_TMP103 is not set # CONFIG_SENSORS_TMP108 is not set CONFIG_SENSORS_TMP401=m CONFIG_SENSORS_TMP421=m CONFIG_SENSORS_VIA_CPUTEMP=m CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_VT8231=m # CONFIG_SENSORS_W83773G is not set CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83795=m # CONFIG_SENSORS_W83795_FANCTRL is not set CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m # CONFIG_SENSORS_XGENE is not set # # ACPI drivers # CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=m CONFIG_THERMAL=y # CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set # CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y # CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not set # CONFIG_CLOCK_THERMAL is not set # CONFIG_DEVFREQ_THERMAL is not set # CONFIG_THERMAL_EMULATION is not set # # Intel thermal drivers # CONFIG_INTEL_POWERCLAMP=m CONFIG_X86_PKG_TEMP_THERMAL=m CONFIG_INTEL_SOC_DTS_IOSF_CORE=m # CONFIG_INTEL_SOC_DTS_THERMAL is not set # # ACPI INT340X thermal drivers # CONFIG_INT340X_THERMAL=m CONFIG_ACPI_THERMAL_REL=m # CONFIG_INT3406_THERMAL is not set # CONFIG_INTEL_PCH_THERMAL is not set # CONFIG_GENERIC_ADC_THERMAL is not set CONFIG_WATCHDOG=y CONFIG_WATCHDOG_CORE=y # CONFIG_WATCHDOG_NOWAYOUT is not set CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y CONFIG_WATCHDOG_SYSFS=y # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_WDAT_WDT=m # CONFIG_XILINX_WATCHDOG is not set # CONFIG_ZIIRAVE_WATCHDOG is not set # CONFIG_CADENCE_WATCHDOG is not set # CONFIG_DW_WATCHDOG is not set # CONFIG_MAX63XX_WATCHDOG is not set # CONFIG_ACQUIRE_WDT is not set # CONFIG_ADVANTECH_WDT is not set CONFIG_ALIM1535_WDT=m CONFIG_ALIM7101_WDT=m # CONFIG_EBC_C384_WDT is not set CONFIG_F71808E_WDT=m CONFIG_SP5100_TCO=m CONFIG_SBC_FITPC2_WATCHDOG=m # CONFIG_EUROTECH_WDT is not set CONFIG_IB700_WDT=m CONFIG_IBMASR=m # CONFIG_WAFER_WDT is not set CONFIG_I6300ESB_WDT=y CONFIG_IE6XX_WDT=m CONFIG_ITCO_WDT=y CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_IT8712F_WDT=m CONFIG_IT87_WDT=m CONFIG_HP_WATCHDOG=m CONFIG_HPWDT_NMI_DECODING=y # CONFIG_SC1200_WDT is not set # CONFIG_PC87413_WDT is not set CONFIG_NV_TCO=m # CONFIG_60XX_WDT is not set # CONFIG_CPU5_WDT is not set CONFIG_SMSC_SCH311X_WDT=m # CONFIG_SMSC37B787_WDT is not set # CONFIG_TQMX86_WDT is not set CONFIG_VIA_WDT=m CONFIG_W83627HF_WDT=m CONFIG_W83877F_WDT=m CONFIG_W83977F_WDT=m CONFIG_MACHZ_WDT=m # CONFIG_SBC_EPX_C3_WATCHDOG is not set CONFIG_INTEL_MEI_WDT=m # CONFIG_NI903X_WDT is not set # CONFIG_NIC7018_WDT is not set # CONFIG_MEN_A21_WDT is not set CONFIG_XEN_WDT=m # # PCI-based Watchdog Cards # CONFIG_PCIPCWATCHDOG=m CONFIG_WDTPCI=m # # USB-based Watchdog Cards # CONFIG_USBPCWATCHDOG=m # # Watchdog Pretimeout Governors # # CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set CONFIG_SSB_POSSIBLE=y CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_SDIOHOST_POSSIBLE=y CONFIG_SSB_SDIOHOST=y CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y CONFIG_SSB_DRIVER_GPIO=y CONFIG_BCMA_POSSIBLE=y CONFIG_BCMA=m CONFIG_BCMA_HOST_PCI_POSSIBLE=y CONFIG_BCMA_HOST_PCI=y # CONFIG_BCMA_HOST_SOC is not set CONFIG_BCMA_DRIVER_PCI=y CONFIG_BCMA_DRIVER_GMAC_CMN=y CONFIG_BCMA_DRIVER_GPIO=y # CONFIG_BCMA_DEBUG is not set # # Multifunction device drivers # CONFIG_MFD_CORE=y # CONFIG_MFD_AS3711 is not set # CONFIG_PMIC_ADP5520 is not set # CONFIG_MFD_AAT2870_CORE is not set # CONFIG_MFD_BCM590XX is not set # CONFIG_MFD_BD9571MWV is not set # CONFIG_MFD_AXP20X_I2C is not set # CONFIG_MFD_CROS_EC is not set # CONFIG_MFD_MADERA is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_DA9052_SPI is not set # CONFIG_MFD_DA9052_I2C is not set # CONFIG_MFD_DA9055 is not set # CONFIG_MFD_DA9062 is not set # CONFIG_MFD_DA9063 is not set # CONFIG_MFD_DA9150 is not set # CONFIG_MFD_DLN2 is not set # CONFIG_MFD_MC13XXX_SPI is not set # CONFIG_MFD_MC13XXX_I2C is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_HTC_I2CPLD is not set # CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not set CONFIG_LPC_ICH=m CONFIG_LPC_SCH=m # CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not set CONFIG_MFD_INTEL_LPSS=y CONFIG_MFD_INTEL_LPSS_ACPI=y CONFIG_MFD_INTEL_LPSS_PCI=y # CONFIG_MFD_JANZ_CMODIO is not set # CONFIG_MFD_KEMPLD is not set # CONFIG_MFD_88PM800 is not set # CONFIG_MFD_88PM805 is not set # CONFIG_MFD_88PM860X is not set # CONFIG_MFD_MAX14577 is not set # CONFIG_MFD_MAX77693 is not set # CONFIG_MFD_MAX77843 is not set # CONFIG_MFD_MAX8907 is not set # CONFIG_MFD_MAX8925 is not set # CONFIG_MFD_MAX8997 is not set # CONFIG_MFD_MAX8998 is not set # CONFIG_MFD_MT6397 is not set # CONFIG_MFD_MENF21BMC is not set # CONFIG_EZX_PCAP is not set CONFIG_MFD_VIPERBOARD=m # CONFIG_MFD_RETU is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_UCB1400_CORE is not set # CONFIG_MFD_RDC321X is not set # CONFIG_MFD_RT5033 is not set # CONFIG_MFD_RC5T583 is not set # CONFIG_MFD_SEC_CORE is not set # CONFIG_MFD_SI476X_CORE is not set CONFIG_MFD_SM501=m CONFIG_MFD_SM501_GPIO=y # CONFIG_MFD_SKY81452 is not set # CONFIG_MFD_SMSC is not set # CONFIG_ABX500_CORE is not set # CONFIG_MFD_SYSCON is not set # CONFIG_MFD_TI_AM335X_TSCADC is not set # CONFIG_MFD_LP3943 is not set # CONFIG_MFD_LP8788 is not set # CONFIG_MFD_TI_LMU is not set # CONFIG_MFD_PALMAS is not set # CONFIG_TPS6105X is not set # CONFIG_TPS65010 is not set # CONFIG_TPS6507X is not set # CONFIG_MFD_TPS65086 is not set # CONFIG_MFD_TPS65090 is not set # CONFIG_MFD_TI_LP873X is not set # CONFIG_MFD_TPS6586X is not set # CONFIG_MFD_TPS65910 is not set # CONFIG_MFD_TPS65912_I2C is not set # CONFIG_MFD_TPS65912_SPI is not set # CONFIG_MFD_TPS80031 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_TWL6040_CORE is not set # CONFIG_MFD_WL1273_CORE is not set # CONFIG_MFD_LM3533 is not set # CONFIG_MFD_TQMX86 is not set CONFIG_MFD_VX855=m # CONFIG_MFD_ARIZONA_I2C is not set # CONFIG_MFD_ARIZONA_SPI is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM831X_I2C is not set # CONFIG_MFD_WM831X_SPI is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_WM8994 is not set # CONFIG_REGULATOR is not set CONFIG_RC_CORE=m CONFIG_RC_MAP=m CONFIG_LIRC=y CONFIG_RC_DECODERS=y CONFIG_IR_NEC_DECODER=m CONFIG_IR_RC5_DECODER=m CONFIG_IR_RC6_DECODER=m CONFIG_IR_JVC_DECODER=m CONFIG_IR_SONY_DECODER=m CONFIG_IR_SANYO_DECODER=m CONFIG_IR_SHARP_DECODER=m CONFIG_IR_MCE_KBD_DECODER=m # CONFIG_IR_XMP_DECODER is not set # CONFIG_IR_IMON_DECODER is not set # CONFIG_IR_RCMM_DECODER is not set CONFIG_RC_DEVICES=y CONFIG_RC_ATI_REMOTE=m CONFIG_IR_ENE=m CONFIG_IR_IMON=m # CONFIG_IR_IMON_RAW is not set CONFIG_IR_MCEUSB=m CONFIG_IR_ITE_CIR=m CONFIG_IR_FINTEK=m CONFIG_IR_NUVOTON=m CONFIG_IR_REDRAT3=m CONFIG_IR_STREAMZAP=m CONFIG_IR_WINBOND_CIR=m # CONFIG_IR_IGORPLUGUSB is not set CONFIG_IR_IGUANA=m CONFIG_IR_TTUSBIR=m CONFIG_RC_LOOPBACK=m # CONFIG_IR_SERIAL is not set # CONFIG_IR_SIR is not set # CONFIG_RC_XBOX_DVD is not set CONFIG_MEDIA_SUPPORT=m # # Multimedia core support # CONFIG_MEDIA_CAMERA_SUPPORT=y CONFIG_MEDIA_ANALOG_TV_SUPPORT=y CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y CONFIG_MEDIA_RADIO_SUPPORT=y # CONFIG_MEDIA_SDR_SUPPORT is not set # CONFIG_MEDIA_CEC_SUPPORT is not set # CONFIG_MEDIA_CONTROLLER is not set CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2=m # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_TUNER=m CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_VMALLOC=m CONFIG_DVB_CORE=m # CONFIG_DVB_MMAP is not set CONFIG_DVB_NET=y CONFIG_TTPCI_EEPROM=m CONFIG_DVB_MAX_ADAPTERS=8 CONFIG_DVB_DYNAMIC_MINORS=y # CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set # CONFIG_DVB_ULE_DEBUG is not set # # Media drivers # CONFIG_MEDIA_USB_SUPPORT=y # # Webcam devices # CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_USB_M5602=m CONFIG_USB_STV06XX=m CONFIG_USB_GL860=m CONFIG_USB_GSPCA_BENQ=m CONFIG_USB_GSPCA_CONEX=m CONFIG_USB_GSPCA_CPIA1=m # CONFIG_USB_GSPCA_DTCS033 is not set CONFIG_USB_GSPCA_ETOMS=m CONFIG_USB_GSPCA_FINEPIX=m CONFIG_USB_GSPCA_JEILINJ=m CONFIG_USB_GSPCA_JL2005BCD=m # CONFIG_USB_GSPCA_KINECT is not set CONFIG_USB_GSPCA_KONICA=m CONFIG_USB_GSPCA_MARS=m CONFIG_USB_GSPCA_MR97310A=m CONFIG_USB_GSPCA_NW80X=m CONFIG_USB_GSPCA_OV519=m CONFIG_USB_GSPCA_OV534=m CONFIG_USB_GSPCA_OV534_9=m CONFIG_USB_GSPCA_PAC207=m CONFIG_USB_GSPCA_PAC7302=m CONFIG_USB_GSPCA_PAC7311=m CONFIG_USB_GSPCA_SE401=m CONFIG_USB_GSPCA_SN9C2028=m CONFIG_USB_GSPCA_SN9C20X=m CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m CONFIG_USB_GSPCA_SPCA500=m CONFIG_USB_GSPCA_SPCA501=m CONFIG_USB_GSPCA_SPCA505=m CONFIG_USB_GSPCA_SPCA506=m CONFIG_USB_GSPCA_SPCA508=m CONFIG_USB_GSPCA_SPCA561=m CONFIG_USB_GSPCA_SPCA1528=m CONFIG_USB_GSPCA_SQ905=m CONFIG_USB_GSPCA_SQ905C=m CONFIG_USB_GSPCA_SQ930X=m CONFIG_USB_GSPCA_STK014=m # CONFIG_USB_GSPCA_STK1135 is not set CONFIG_USB_GSPCA_STV0680=m CONFIG_USB_GSPCA_SUNPLUS=m CONFIG_USB_GSPCA_T613=m CONFIG_USB_GSPCA_TOPRO=m # CONFIG_USB_GSPCA_TOUPTEK is not set CONFIG_USB_GSPCA_TV8532=m CONFIG_USB_GSPCA_VC032X=m CONFIG_USB_GSPCA_VICAM=m CONFIG_USB_GSPCA_XIRLINK_CIT=m CONFIG_USB_GSPCA_ZC3XX=m CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_PWC_INPUT_EVDEV=y # CONFIG_VIDEO_CPIA2 is not set CONFIG_USB_ZR364XX=m CONFIG_USB_STKWEBCAM=m CONFIG_USB_S2255=m # CONFIG_VIDEO_USBTV is not set # # Analog TV USB devices # CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_HDPVR=m CONFIG_VIDEO_USBVISION=m # CONFIG_VIDEO_STK1160_COMMON is not set # CONFIG_VIDEO_GO7007 is not set # # Analog/digital TV USB devices # CONFIG_VIDEO_AU0828=m CONFIG_VIDEO_AU0828_V4L2=y # CONFIG_VIDEO_AU0828_RC is not set CONFIG_VIDEO_CX231XX=m CONFIG_VIDEO_CX231XX_RC=y CONFIG_VIDEO_CX231XX_ALSA=m CONFIG_VIDEO_CX231XX_DVB=m CONFIG_VIDEO_TM6000=m CONFIG_VIDEO_TM6000_ALSA=m CONFIG_VIDEO_TM6000_DVB=m # # Digital TV USB devices # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_DIB3000MC=m CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_PCTV452E=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_CINERGY_T2=m CONFIG_DVB_USB_DTV5100=m CONFIG_DVB_USB_AZ6027=m CONFIG_DVB_USB_TECHNISAT_USB2=m CONFIG_DVB_USB_V2=m CONFIG_DVB_USB_AF9015=m CONFIG_DVB_USB_AF9035=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_AZ6007=m CONFIG_DVB_USB_CE6230=m CONFIG_DVB_USB_EC168=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_LME2510=m CONFIG_DVB_USB_MXL111SF=m CONFIG_DVB_USB_RTL28XXU=m # CONFIG_DVB_USB_DVBSKY is not set # CONFIG_DVB_USB_ZD1301 is not set CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_SMS_USB_DRV=m CONFIG_DVB_B2C2_FLEXCOP_USB=m # CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set # CONFIG_DVB_AS102 is not set # # Webcam, TV (analog/digital) USB devices # CONFIG_VIDEO_EM28XX=m # CONFIG_VIDEO_EM28XX_V4L2 is not set CONFIG_VIDEO_EM28XX_ALSA=m CONFIG_VIDEO_EM28XX_DVB=m CONFIG_VIDEO_EM28XX_RC=m CONFIG_MEDIA_PCI_SUPPORT=y # # Media capture support # # CONFIG_VIDEO_MEYE is not set # CONFIG_VIDEO_SOLO6X10 is not set # CONFIG_VIDEO_TW5864 is not set # CONFIG_VIDEO_TW68 is not set # CONFIG_VIDEO_TW686X is not set # # Media capture/analog TV support # CONFIG_VIDEO_IVTV=m # CONFIG_VIDEO_IVTV_DEPRECATED_IOCTLS is not set # CONFIG_VIDEO_IVTV_ALSA is not set CONFIG_VIDEO_FB_IVTV=m # CONFIG_VIDEO_FB_IVTV_FORCE_PAT is not set # CONFIG_VIDEO_HEXIUM_GEMINI is not set # CONFIG_VIDEO_HEXIUM_ORION is not set # CONFIG_VIDEO_MXB is not set # CONFIG_VIDEO_DT3155 is not set # # Media capture/analog/hybrid TV support # CONFIG_VIDEO_CX18=m CONFIG_VIDEO_CX18_ALSA=m CONFIG_VIDEO_CX23885=m CONFIG_MEDIA_ALTERA_CI=m # CONFIG_VIDEO_CX25821 is not set CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_ENABLE_VP3054=y CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX88_MPEG=m CONFIG_VIDEO_BT848=m CONFIG_DVB_BT8XX=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_RC=y CONFIG_VIDEO_SAA7134_DVB=m CONFIG_VIDEO_SAA7164=m # # Media digital TV PCI Adapters # CONFIG_DVB_AV7110_IR=y CONFIG_DVB_AV7110=m CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m CONFIG_DVB_B2C2_FLEXCOP_PCI=m # CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set CONFIG_DVB_PLUTO2=m CONFIG_DVB_DM1105=m CONFIG_DVB_PT1=m # CONFIG_DVB_PT3 is not set CONFIG_MANTIS_CORE=m CONFIG_DVB_MANTIS=m CONFIG_DVB_HOPPER=m CONFIG_DVB_NGENE=m CONFIG_DVB_DDBRIDGE=m # CONFIG_DVB_DDBRIDGE_MSIENABLE is not set # CONFIG_DVB_SMIPCIE is not set # CONFIG_DVB_NETUP_UNIDVB is not set # CONFIG_V4L_PLATFORM_DRIVERS is not set # CONFIG_V4L_MEM2MEM_DRIVERS is not set # CONFIG_V4L_TEST_DRIVERS is not set # CONFIG_DVB_PLATFORM_DRIVERS is not set # # Supported MMC/SDIO adapters # CONFIG_SMS_SDIO_DRV=m CONFIG_RADIO_ADAPTERS=y CONFIG_RADIO_TEA575X=m # CONFIG_RADIO_SI470X is not set # CONFIG_RADIO_SI4713 is not set # CONFIG_USB_MR800 is not set # CONFIG_USB_DSBR is not set # CONFIG_RADIO_MAXIRADIO is not set # CONFIG_RADIO_SHARK is not set # CONFIG_RADIO_SHARK2 is not set # CONFIG_USB_KEENE is not set # CONFIG_USB_RAREMONO is not set # CONFIG_USB_MA901 is not set # CONFIG_RADIO_TEA5764 is not set # CONFIG_RADIO_SAA7706H is not set # CONFIG_RADIO_TEF6862 is not set # CONFIG_RADIO_WL1273 is not set # # Texas Instruments WL128x FM driver (ST based) # # # Supported FireWire (IEEE 1394) Adapters # CONFIG_DVB_FIREDTV=m CONFIG_DVB_FIREDTV_INPUT=y CONFIG_MEDIA_COMMON_OPTIONS=y # # common driver options # CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_TVEEPROM=m CONFIG_CYPRESS_FIRMWARE=m CONFIG_VIDEOBUF2_CORE=m CONFIG_VIDEOBUF2_V4L2=m CONFIG_VIDEOBUF2_MEMOPS=m CONFIG_VIDEOBUF2_VMALLOC=m CONFIG_VIDEOBUF2_DMA_SG=m CONFIG_VIDEOBUF2_DVB=m CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_SMS_SIANO_MDTV=m CONFIG_SMS_SIANO_RC=y # CONFIG_SMS_SIANO_DEBUGFS is not set # # Media ancillary drivers (tuners, sensors, i2c, spi, frontends) # CONFIG_MEDIA_SUBDRV_AUTOSELECT=y CONFIG_MEDIA_ATTACH=y CONFIG_VIDEO_IR_I2C=m # # Audio decoders, processors and mixers # CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS3308=m CONFIG_VIDEO_CS5345=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_WM8739=m CONFIG_VIDEO_VP27SMPX=m # # RDS decoders # CONFIG_VIDEO_SAA6588=m # # Video decoders # CONFIG_VIDEO_SAA711X=m # # Video and audio decoders # CONFIG_VIDEO_SAA717X=m CONFIG_VIDEO_CX25840=m # # Video encoders # CONFIG_VIDEO_SAA7127=m # # Camera sensor devices # # # Flash devices # # # Video improvement chips # CONFIG_VIDEO_UPD64031A=m CONFIG_VIDEO_UPD64083=m # # Audio/Video compression chips # CONFIG_VIDEO_SAA6752HS=m # # SDR tuner chips # # # Miscellaneous helper chips # CONFIG_VIDEO_M52790=m # # Media SPI Adapters # # CONFIG_CXD2880_SPI_DRV is not set CONFIG_MEDIA_TUNER=m CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA18250=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2063=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_MT2131=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_XC4000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_MEDIA_TUNER_MC44S803=m CONFIG_MEDIA_TUNER_MAX2165=m CONFIG_MEDIA_TUNER_TDA18218=m CONFIG_MEDIA_TUNER_FC0011=m CONFIG_MEDIA_TUNER_FC0012=m CONFIG_MEDIA_TUNER_FC0013=m CONFIG_MEDIA_TUNER_TDA18212=m CONFIG_MEDIA_TUNER_E4000=m CONFIG_MEDIA_TUNER_FC2580=m CONFIG_MEDIA_TUNER_M88RS6000T=m CONFIG_MEDIA_TUNER_TUA9001=m CONFIG_MEDIA_TUNER_SI2157=m CONFIG_MEDIA_TUNER_IT913X=m CONFIG_MEDIA_TUNER_R820T=m CONFIG_MEDIA_TUNER_QM1D1C0042=m CONFIG_MEDIA_TUNER_QM1D1B0004=m # # Multistandard (satellite) frontends # CONFIG_DVB_STB0899=m CONFIG_DVB_STB6100=m CONFIG_DVB_STV090x=m CONFIG_DVB_STV0910=m CONFIG_DVB_STV6110x=m CONFIG_DVB_STV6111=m CONFIG_DVB_MXL5XX=m CONFIG_DVB_M88DS3103=m # # Multistandard (cable + terrestrial) frontends # CONFIG_DVB_DRXK=m CONFIG_DVB_TDA18271C2DD=m CONFIG_DVB_SI2165=m CONFIG_DVB_MN88472=m CONFIG_DVB_MN88473=m # # DVB-S (satellite) frontends # CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_ZL10036=m CONFIG_DVB_ZL10039=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0288=m CONFIG_DVB_STB6000=m CONFIG_DVB_STV0299=m CONFIG_DVB_STV6110=m CONFIG_DVB_STV0900=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_TDA8261=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TUNER_CX24113=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m CONFIG_DVB_CX24116=m CONFIG_DVB_CX24117=m CONFIG_DVB_CX24120=m CONFIG_DVB_SI21XX=m CONFIG_DVB_TS2020=m CONFIG_DVB_DS3000=m CONFIG_DVB_MB86A16=m CONFIG_DVB_TDA10071=m # # DVB-T (terrestrial) frontends # CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m CONFIG_DVB_DRXD=m CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m CONFIG_DVB_AF9013=m CONFIG_DVB_EC100=m CONFIG_DVB_STV0367=m CONFIG_DVB_CXD2820R=m CONFIG_DVB_CXD2841ER=m CONFIG_DVB_RTL2830=m CONFIG_DVB_RTL2832=m CONFIG_DVB_SI2168=m CONFIG_DVB_GP8PSK_FE=m # # DVB-C (cable) frontends # CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m # # ATSC (North American/Korean Terrestrial/Cable DTV) frontends # CONFIG_DVB_NXT200X=m CONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_LGDT3305=m CONFIG_DVB_LGDT3306A=m CONFIG_DVB_LG2160=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_AU8522_DTV=m CONFIG_DVB_AU8522_V4L=m CONFIG_DVB_S5H1411=m # # ISDB-T (terrestrial) frontends # CONFIG_DVB_S921=m CONFIG_DVB_DIB8000=m CONFIG_DVB_MB86A20S=m # # ISDB-S (satellite) & ISDB-T (terrestrial) frontends # CONFIG_DVB_TC90522=m # # Digital terrestrial only tuners/PLL # CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m CONFIG_DVB_TUNER_DIB0090=m # # SEC control devices for DVB-S # CONFIG_DVB_DRX39XYJ=m CONFIG_DVB_LNBH25=m CONFIG_DVB_LNBP21=m CONFIG_DVB_LNBP22=m CONFIG_DVB_ISL6405=m CONFIG_DVB_ISL6421=m CONFIG_DVB_ISL6423=m CONFIG_DVB_A8293=m CONFIG_DVB_LGS8GXX=m CONFIG_DVB_ATBM8830=m CONFIG_DVB_TDA665x=m CONFIG_DVB_IX2505V=m CONFIG_DVB_M88RS2000=m CONFIG_DVB_AF9033=m # # Common Interface (EN50221) controller drivers # CONFIG_DVB_CXD2099=m # # Tools to develop new frontends # CONFIG_DVB_DUMMY_FE=m # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=y CONFIG_AGP_SIS=y CONFIG_AGP_VIA=y CONFIG_INTEL_GTT=y CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=64 CONFIG_VGA_SWITCHEROO=y CONFIG_DRM=m CONFIG_DRM_MIPI_DSI=y CONFIG_DRM_DP_AUX_CHARDEV=y CONFIG_DRM_DEBUG_SELFTEST=m CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_KMS_FB_HELPER=y CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 # CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set CONFIG_DRM_LOAD_EDID_FIRMWARE=y # CONFIG_DRM_DP_CEC is not set CONFIG_DRM_TTM=m CONFIG_DRM_VM=y CONFIG_DRM_SCHED=m # # I2C encoder or helper chips # CONFIG_DRM_I2C_CH7006=m CONFIG_DRM_I2C_SIL164=m # CONFIG_DRM_I2C_NXP_TDA998X is not set # CONFIG_DRM_I2C_NXP_TDA9950 is not set # # ARM devices # CONFIG_DRM_RADEON=m # CONFIG_DRM_RADEON_USERPTR is not set CONFIG_DRM_AMDGPU=m # CONFIG_DRM_AMDGPU_SI is not set # CONFIG_DRM_AMDGPU_CIK is not set # CONFIG_DRM_AMDGPU_USERPTR is not set # CONFIG_DRM_AMDGPU_GART_DEBUGFS is not set # # ACP (Audio CoProcessor) Configuration # # CONFIG_DRM_AMD_ACP is not set # # Display Engine Configuration # CONFIG_DRM_AMD_DC=y CONFIG_DRM_AMD_DC_DCN1_0=y CONFIG_DRM_AMD_DC_DCN1_01=y # CONFIG_DEBUG_KERNEL_DC is not set # CONFIG_HSA_AMD is not set # # AMD Library routines # CONFIG_CHASH=m # CONFIG_CHASH_STATS is not set # CONFIG_CHASH_SELFTEST is not set CONFIG_DRM_NOUVEAU=m CONFIG_NOUVEAU_DEBUG=5 CONFIG_NOUVEAU_DEBUG_DEFAULT=3 # CONFIG_NOUVEAU_DEBUG_MMU is not set CONFIG_DRM_NOUVEAU_BACKLIGHT=y # CONFIG_DRM_NOUVEAU_SVM is not set CONFIG_DRM_I915=m # CONFIG_DRM_I915_ALPHA_SUPPORT is not set CONFIG_DRM_I915_CAPTURE_ERROR=y CONFIG_DRM_I915_COMPRESS_ERROR=y CONFIG_DRM_I915_USERPTR=y CONFIG_DRM_I915_GVT=y CONFIG_DRM_I915_GVT_KVMGT=m # # drm/i915 Debugging # # CONFIG_DRM_I915_WERROR is not set # CONFIG_DRM_I915_DEBUG is not set # CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set # CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set # CONFIG_DRM_I915_DEBUG_GUC is not set # CONFIG_DRM_I915_SELFTEST is not set # CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set # CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set # CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set CONFIG_DRM_VGEM=m # CONFIG_DRM_VKMS is not set CONFIG_DRM_VMWGFX=m CONFIG_DRM_VMWGFX_FBCON=y CONFIG_DRM_GMA500=m CONFIG_DRM_GMA600=y CONFIG_DRM_GMA3600=y CONFIG_DRM_UDL=m CONFIG_DRM_AST=m CONFIG_DRM_MGAG200=m CONFIG_DRM_CIRRUS_QEMU=m CONFIG_DRM_QXL=m CONFIG_DRM_BOCHS=m CONFIG_DRM_VIRTIO_GPU=m CONFIG_DRM_PANEL=y # # Display Panels # # CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set CONFIG_DRM_BRIDGE=y CONFIG_DRM_PANEL_BRIDGE=y # # Display Interface Bridges # # CONFIG_DRM_ANALOGIX_ANX78XX is not set # CONFIG_DRM_ETNAVIV is not set # CONFIG_DRM_HISI_HIBMC is not set # CONFIG_DRM_TINYDRM is not set # CONFIG_DRM_XEN is not set # CONFIG_DRM_LEGACY is not set CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y CONFIG_DRM_LIB_RANDOM=y # # Frame buffer Devices # CONFIG_FB_CMDLINE=y CONFIG_FB_NOTIFY=y CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y # CONFIG_FB_MODE_HELPERS is not set CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_UVESA is not set CONFIG_FB_VESA=y CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_OPENCORES is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_SM501 is not set # CONFIG_FB_SMSCUFX is not set # CONFIG_FB_UDL is not set # CONFIG_FB_IBM_GXT4500 is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_XEN_FBDEV_FRONTEND is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set CONFIG_FB_HYPERV=m # CONFIG_FB_SIMPLE is not set # CONFIG_FB_SM712 is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=m # CONFIG_LCD_L4F00242T03 is not set # CONFIG_LCD_LMS283GF05 is not set # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_ILI922X is not set # CONFIG_LCD_ILI9320 is not set # CONFIG_LCD_TDO24M is not set # CONFIG_LCD_VGG2432A4 is not set CONFIG_LCD_PLATFORM=m # CONFIG_LCD_AMS369FG06 is not set # CONFIG_LCD_LMS501KF03 is not set # CONFIG_LCD_HX8357 is not set # CONFIG_LCD_OTM3225A is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_GENERIC is not set # CONFIG_BACKLIGHT_PWM is not set CONFIG_BACKLIGHT_APPLE=m # CONFIG_BACKLIGHT_PM8941_WLED is not set # CONFIG_BACKLIGHT_SAHARA is not set # CONFIG_BACKLIGHT_ADP8860 is not set # CONFIG_BACKLIGHT_ADP8870 is not set # CONFIG_BACKLIGHT_LM3630A is not set # CONFIG_BACKLIGHT_LM3639 is not set CONFIG_BACKLIGHT_LP855X=m # CONFIG_BACKLIGHT_GPIO is not set # CONFIG_BACKLIGHT_LV5207LP is not set # CONFIG_BACKLIGHT_BD6107 is not set # CONFIG_BACKLIGHT_ARCXCNN is not set CONFIG_HDMI=y # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64 # CONFIG_VGACON_SOFT_SCROLLBACK_PERSISTENT_ENABLE_BY_DEFAULT is not set CONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y # CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y CONFIG_SOUND=m CONFIG_SOUND_OSS_CORE=y CONFIG_SOUND_OSS_CORE_PRECLAIM=y CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_PCM_ELD=y CONFIG_SND_HWDEP=m CONFIG_SND_SEQ_DEVICE=m CONFIG_SND_RAWMIDI=m CONFIG_SND_COMPRESS_OFFLOAD=m CONFIG_SND_JACK=y CONFIG_SND_JACK_INPUT_DEV=y CONFIG_SND_OSSEMUL=y # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set CONFIG_SND_PCM_TIMER=y CONFIG_SND_HRTIMER=m CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_MAX_CARDS=32 # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_PROC_FS=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_DMA_SGBUF=y CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_SEQUENCER_OSS=m CONFIG_SND_SEQ_HRTIMER_DEFAULT=y CONFIG_SND_SEQ_MIDI_EVENT=m CONFIG_SND_SEQ_MIDI=m CONFIG_SND_SEQ_MIDI_EMUL=m CONFIG_SND_SEQ_VIRMIDI=m CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_OPL3_LIB_SEQ=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y CONFIG_SND_PCSP=m CONFIG_SND_DUMMY=m CONFIG_SND_ALOOP=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m # CONFIG_SND_MTS64 is not set # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m # CONFIG_SND_PORTMAN2X4 is not set CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=5 CONFIG_SND_PCI=y CONFIG_SND_AD1889=m # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set CONFIG_SND_ALI5451=m CONFIG_SND_ASIHPI=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m # CONFIG_SND_AW2 is not set # CONFIG_SND_AZT3328 is not set CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_OXYGEN_LIB=m CONFIG_SND_OXYGEN=m # CONFIG_SND_CS4281 is not set CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CTXFI=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_INDIGOIOX=m CONFIG_SND_INDIGODJX=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1_SEQ=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m # CONFIG_SND_ES1938 is not set CONFIG_SND_ES1968=m CONFIG_SND_ES1968_INPUT=y CONFIG_SND_ES1968_RADIO=y # CONFIG_SND_FM801 is not set CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_LOLA=m CONFIG_SND_LX6464ES=m CONFIG_SND_MAESTRO3=m CONFIG_SND_MAESTRO3_INPUT=y CONFIG_SND_MIXART=m # CONFIG_SND_NM256 is not set CONFIG_SND_PCXHR=m # CONFIG_SND_RIPTIDE is not set CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m # CONFIG_SND_SONICVIBES is not set CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VIRTUOSO=m CONFIG_SND_VX222=m # CONFIG_SND_YMFPCI is not set # # HD-Audio # CONFIG_SND_HDA=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_BEEP_MODE=0 CONFIG_SND_HDA_PATCH_LOADER=y CONFIG_SND_HDA_CODEC_REALTEK=m CONFIG_SND_HDA_CODEC_ANALOG=m CONFIG_SND_HDA_CODEC_SIGMATEL=m CONFIG_SND_HDA_CODEC_VIA=m CONFIG_SND_HDA_CODEC_HDMI=m CONFIG_SND_HDA_CODEC_CIRRUS=m CONFIG_SND_HDA_CODEC_CONEXANT=m CONFIG_SND_HDA_CODEC_CA0110=m CONFIG_SND_HDA_CODEC_CA0132=m CONFIG_SND_HDA_CODEC_CA0132_DSP=y CONFIG_SND_HDA_CODEC_CMEDIA=m CONFIG_SND_HDA_CODEC_SI3054=m CONFIG_SND_HDA_GENERIC=m CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0 CONFIG_SND_HDA_CORE=m CONFIG_SND_HDA_DSP_LOADER=y CONFIG_SND_HDA_COMPONENT=y CONFIG_SND_HDA_I915=y CONFIG_SND_HDA_EXT_CORE=m CONFIG_SND_HDA_PREALLOC_SIZE=512 # CONFIG_SND_SPI is not set CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_UA101=m CONFIG_SND_USB_USX2Y=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_USB_US122L=m CONFIG_SND_USB_6FIRE=m CONFIG_SND_USB_HIFACE=m CONFIG_SND_BCD2000=m CONFIG_SND_USB_LINE6=m CONFIG_SND_USB_POD=m CONFIG_SND_USB_PODHD=m CONFIG_SND_USB_TONEPORT=m CONFIG_SND_USB_VARIAX=m CONFIG_SND_FIREWIRE=y CONFIG_SND_FIREWIRE_LIB=m # CONFIG_SND_DICE is not set # CONFIG_SND_OXFW is not set CONFIG_SND_ISIGHT=m # CONFIG_SND_FIREWORKS is not set # CONFIG_SND_BEBOB is not set # CONFIG_SND_FIREWIRE_DIGI00X is not set # CONFIG_SND_FIREWIRE_TASCAM is not set # CONFIG_SND_FIREWIRE_MOTU is not set # CONFIG_SND_FIREFACE is not set CONFIG_SND_SOC=m CONFIG_SND_SOC_COMPRESS=y CONFIG_SND_SOC_TOPOLOGY=y CONFIG_SND_SOC_ACPI=m # CONFIG_SND_SOC_AMD_ACP is not set # CONFIG_SND_SOC_AMD_ACP3x is not set # CONFIG_SND_ATMEL_SOC is not set # CONFIG_SND_DESIGNWARE_I2S is not set # # SoC Audio for Freescale CPUs # # # Common SoC Audio options for Freescale CPUs: # # CONFIG_SND_SOC_FSL_ASRC is not set # CONFIG_SND_SOC_FSL_SAI is not set # CONFIG_SND_SOC_FSL_SSI is not set # CONFIG_SND_SOC_FSL_SPDIF is not set # CONFIG_SND_SOC_FSL_ESAI is not set # CONFIG_SND_SOC_FSL_MICFIL is not set # CONFIG_SND_SOC_IMX_AUDMUX is not set # CONFIG_SND_I2S_HI6210_I2S is not set # CONFIG_SND_SOC_IMG is not set CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SST_IPC=m CONFIG_SND_SST_IPC_ACPI=m CONFIG_SND_SOC_INTEL_SST_ACPI=m CONFIG_SND_SOC_INTEL_SST=m CONFIG_SND_SOC_INTEL_SST_FIRMWARE=m CONFIG_SND_SOC_INTEL_HASWELL=m CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m # CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m CONFIG_SND_SOC_INTEL_SKYLAKE=m CONFIG_SND_SOC_INTEL_SKL=m CONFIG_SND_SOC_INTEL_APL=m CONFIG_SND_SOC_INTEL_KBL=m CONFIG_SND_SOC_INTEL_GLK=m CONFIG_SND_SOC_INTEL_CNL=m CONFIG_SND_SOC_INTEL_CFL=m CONFIG_SND_SOC_INTEL_SKYLAKE_FAMILY=m CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m # CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC is not set CONFIG_SND_SOC_INTEL_SKYLAKE_COMMON=m CONFIG_SND_SOC_ACPI_INTEL_MATCH=m CONFIG_SND_SOC_INTEL_MACH=y CONFIG_SND_SOC_INTEL_HASWELL_MACH=m CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m # CONFIG_SND_SOC_INTEL_CHT_BSW_NAU8824_MACH is not set CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=m CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set # CONFIG_SND_SOC_INTEL_GLK_RT5682_MAX98357A_MACH is not set # CONFIG_SND_SOC_MTK_BTCVSD is not set # # STMicroelectronics STM32 SOC audio support # # CONFIG_SND_SOC_XILINX_I2S is not set # CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set # CONFIG_SND_SOC_XILINX_SPDIF is not set # CONFIG_SND_SOC_XTFPGA_I2S is not set # CONFIG_ZX_TDM is not set CONFIG_SND_SOC_I2C_AND_SPI=m # # CODEC drivers # # CONFIG_SND_SOC_AC97_CODEC is not set # CONFIG_SND_SOC_ADAU1701 is not set # CONFIG_SND_SOC_ADAU1761_I2C is not set # CONFIG_SND_SOC_ADAU1761_SPI is not set # CONFIG_SND_SOC_ADAU7002 is not set # CONFIG_SND_SOC_AK4104 is not set # CONFIG_SND_SOC_AK4118 is not set # CONFIG_SND_SOC_AK4458 is not set # CONFIG_SND_SOC_AK4554 is not set # CONFIG_SND_SOC_AK4613 is not set # CONFIG_SND_SOC_AK4642 is not set # CONFIG_SND_SOC_AK5386 is not set # CONFIG_SND_SOC_AK5558 is not set # CONFIG_SND_SOC_ALC5623 is not set # CONFIG_SND_SOC_BD28623 is not set # CONFIG_SND_SOC_BT_SCO is not set # CONFIG_SND_SOC_CS35L32 is not set # CONFIG_SND_SOC_CS35L33 is not set # CONFIG_SND_SOC_CS35L34 is not set # CONFIG_SND_SOC_CS35L35 is not set # CONFIG_SND_SOC_CS35L36 is not set # CONFIG_SND_SOC_CS42L42 is not set # CONFIG_SND_SOC_CS42L51_I2C is not set # CONFIG_SND_SOC_CS42L52 is not set # CONFIG_SND_SOC_CS42L56 is not set # CONFIG_SND_SOC_CS42L73 is not set # CONFIG_SND_SOC_CS4265 is not set # CONFIG_SND_SOC_CS4270 is not set # CONFIG_SND_SOC_CS4271_I2C is not set # CONFIG_SND_SOC_CS4271_SPI is not set # CONFIG_SND_SOC_CS42XX8_I2C is not set # CONFIG_SND_SOC_CS43130 is not set # CONFIG_SND_SOC_CS4341 is not set # CONFIG_SND_SOC_CS4349 is not set # CONFIG_SND_SOC_CS53L30 is not set CONFIG_SND_SOC_DA7213=m CONFIG_SND_SOC_DA7219=m CONFIG_SND_SOC_DMIC=m # CONFIG_SND_SOC_ES7134 is not set # CONFIG_SND_SOC_ES7241 is not set CONFIG_SND_SOC_ES8316=m # CONFIG_SND_SOC_ES8328_I2C is not set # CONFIG_SND_SOC_ES8328_SPI is not set # CONFIG_SND_SOC_GTM601 is not set CONFIG_SND_SOC_HDAC_HDMI=m # CONFIG_SND_SOC_INNO_RK3036 is not set # CONFIG_SND_SOC_MAX98088 is not set CONFIG_SND_SOC_MAX98090=m CONFIG_SND_SOC_MAX98357A=m # CONFIG_SND_SOC_MAX98504 is not set # CONFIG_SND_SOC_MAX9867 is not set CONFIG_SND_SOC_MAX98927=m # CONFIG_SND_SOC_MAX98373 is not set # CONFIG_SND_SOC_MAX9860 is not set # CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set # CONFIG_SND_SOC_PCM1681 is not set # CONFIG_SND_SOC_PCM1789_I2C is not set # CONFIG_SND_SOC_PCM179X_I2C is not set # CONFIG_SND_SOC_PCM179X_SPI is not set # CONFIG_SND_SOC_PCM186X_I2C is not set # CONFIG_SND_SOC_PCM186X_SPI is not set # CONFIG_SND_SOC_PCM3060_I2C is not set # CONFIG_SND_SOC_PCM3060_SPI is not set # CONFIG_SND_SOC_PCM3168A_I2C is not set # CONFIG_SND_SOC_PCM3168A_SPI is not set # CONFIG_SND_SOC_PCM512x_I2C is not set # CONFIG_SND_SOC_PCM512x_SPI is not set # CONFIG_SND_SOC_RK3328 is not set CONFIG_SND_SOC_RL6231=m CONFIG_SND_SOC_RL6347A=m CONFIG_SND_SOC_RT286=m CONFIG_SND_SOC_RT298=m CONFIG_SND_SOC_RT5514=m CONFIG_SND_SOC_RT5514_SPI=m # CONFIG_SND_SOC_RT5616 is not set # CONFIG_SND_SOC_RT5631 is not set CONFIG_SND_SOC_RT5640=m CONFIG_SND_SOC_RT5645=m CONFIG_SND_SOC_RT5651=m CONFIG_SND_SOC_RT5663=m CONFIG_SND_SOC_RT5670=m CONFIG_SND_SOC_RT5677=m CONFIG_SND_SOC_RT5677_SPI=m # CONFIG_SND_SOC_SGTL5000 is not set # CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set # CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set # CONFIG_SND_SOC_SPDIF is not set # CONFIG_SND_SOC_SSM2305 is not set # CONFIG_SND_SOC_SSM2602_SPI is not set # CONFIG_SND_SOC_SSM2602_I2C is not set CONFIG_SND_SOC_SSM4567=m # CONFIG_SND_SOC_STA32X is not set # CONFIG_SND_SOC_STA350 is not set # CONFIG_SND_SOC_STI_SAS is not set # CONFIG_SND_SOC_TAS2552 is not set # CONFIG_SND_SOC_TAS5086 is not set # CONFIG_SND_SOC_TAS571X is not set # CONFIG_SND_SOC_TAS5720 is not set # CONFIG_SND_SOC_TAS6424 is not set # CONFIG_SND_SOC_TDA7419 is not set # CONFIG_SND_SOC_TFA9879 is not set # CONFIG_SND_SOC_TLV320AIC23_I2C is not set # CONFIG_SND_SOC_TLV320AIC23_SPI is not set # CONFIG_SND_SOC_TLV320AIC31XX is not set # CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set # CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set # CONFIG_SND_SOC_TLV320AIC3X is not set CONFIG_SND_SOC_TS3A227E=m # CONFIG_SND_SOC_TSCS42XX is not set # CONFIG_SND_SOC_TSCS454 is not set # CONFIG_SND_SOC_WM8510 is not set # CONFIG_SND_SOC_WM8523 is not set # CONFIG_SND_SOC_WM8524 is not set # CONFIG_SND_SOC_WM8580 is not set # CONFIG_SND_SOC_WM8711 is not set # CONFIG_SND_SOC_WM8728 is not set # CONFIG_SND_SOC_WM8731 is not set # CONFIG_SND_SOC_WM8737 is not set # CONFIG_SND_SOC_WM8741 is not set # CONFIG_SND_SOC_WM8750 is not set # CONFIG_SND_SOC_WM8753 is not set # CONFIG_SND_SOC_WM8770 is not set # CONFIG_SND_SOC_WM8776 is not set # CONFIG_SND_SOC_WM8782 is not set # CONFIG_SND_SOC_WM8804_I2C is not set # CONFIG_SND_SOC_WM8804_SPI is not set # CONFIG_SND_SOC_WM8903 is not set # CONFIG_SND_SOC_WM8904 is not set # CONFIG_SND_SOC_WM8960 is not set # CONFIG_SND_SOC_WM8962 is not set # CONFIG_SND_SOC_WM8974 is not set # CONFIG_SND_SOC_WM8978 is not set # CONFIG_SND_SOC_WM8985 is not set # CONFIG_SND_SOC_ZX_AUD96P22 is not set # CONFIG_SND_SOC_MAX9759 is not set # CONFIG_SND_SOC_MT6351 is not set # CONFIG_SND_SOC_MT6358 is not set # CONFIG_SND_SOC_NAU8540 is not set # CONFIG_SND_SOC_NAU8810 is not set # CONFIG_SND_SOC_NAU8822 is not set CONFIG_SND_SOC_NAU8824=m CONFIG_SND_SOC_NAU8825=m # CONFIG_SND_SOC_TPA6130A2 is not set # CONFIG_SND_SIMPLE_CARD is not set CONFIG_SND_X86=y CONFIG_HDMI_LPE_AUDIO=m CONFIG_SND_SYNTH_EMUX=m # CONFIG_SND_XEN_FRONTEND is not set CONFIG_AC97_BUS=m # # HID support # CONFIG_HID=y CONFIG_HID_BATTERY_STRENGTH=y CONFIG_HIDRAW=y CONFIG_UHID=m CONFIG_HID_GENERIC=y # # Special HID drivers # CONFIG_HID_A4TECH=y # CONFIG_HID_ACCUTOUCH is not set CONFIG_HID_ACRUX=m # CONFIG_HID_ACRUX_FF is not set CONFIG_HID_APPLE=y CONFIG_HID_APPLEIR=m # CONFIG_HID_ASUS is not set CONFIG_HID_AUREAL=m CONFIG_HID_BELKIN=y # CONFIG_HID_BETOP_FF is not set # CONFIG_HID_BIGBEN_FF is not set CONFIG_HID_CHERRY=y CONFIG_HID_CHICONY=y # CONFIG_HID_CORSAIR is not set # CONFIG_HID_COUGAR is not set CONFIG_HID_PRODIKEYS=m # CONFIG_HID_CMEDIA is not set # CONFIG_HID_CP2112 is not set CONFIG_HID_CYPRESS=y CONFIG_HID_DRAGONRISE=m # CONFIG_DRAGONRISE_FF is not set # CONFIG_HID_EMS_FF is not set # CONFIG_HID_ELAN is not set CONFIG_HID_ELECOM=m # CONFIG_HID_ELO is not set CONFIG_HID_EZKEY=y # CONFIG_HID_GEMBIRD is not set # CONFIG_HID_GFRM is not set CONFIG_HID_HOLTEK=m # CONFIG_HOLTEK_FF is not set # CONFIG_HID_GT683R is not set CONFIG_HID_KEYTOUCH=m CONFIG_HID_KYE=m CONFIG_HID_UCLOGIC=m CONFIG_HID_WALTOP=m # CONFIG_HID_VIEWSONIC is not set CONFIG_HID_GYRATION=m CONFIG_HID_ICADE=m CONFIG_HID_ITE=y # CONFIG_HID_JABRA is not set CONFIG_HID_TWINHAN=m CONFIG_HID_KENSINGTON=y CONFIG_HID_LCPOWER=m CONFIG_HID_LED=m # CONFIG_HID_LENOVO is not set CONFIG_HID_LOGITECH=y CONFIG_HID_LOGITECH_DJ=m CONFIG_HID_LOGITECH_HIDPP=m # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set # CONFIG_LOGIG940_FF is not set # CONFIG_LOGIWHEELS_FF is not set CONFIG_HID_MAGICMOUSE=y # CONFIG_HID_MALTRON is not set # CONFIG_HID_MAYFLASH is not set CONFIG_HID_REDRAGON=y CONFIG_HID_MICROSOFT=y CONFIG_HID_MONTEREY=y CONFIG_HID_MULTITOUCH=m # CONFIG_HID_NTI is not set CONFIG_HID_NTRIG=y CONFIG_HID_ORTEK=m CONFIG_HID_PANTHERLORD=m # CONFIG_PANTHERLORD_FF is not set # CONFIG_HID_PENMOUNT is not set CONFIG_HID_PETALYNX=m CONFIG_HID_PICOLCD=m CONFIG_HID_PICOLCD_FB=y CONFIG_HID_PICOLCD_BACKLIGHT=y CONFIG_HID_PICOLCD_LCD=y CONFIG_HID_PICOLCD_LEDS=y CONFIG_HID_PICOLCD_CIR=y CONFIG_HID_PLANTRONICS=y CONFIG_HID_PRIMAX=m # CONFIG_HID_RETRODE is not set CONFIG_HID_ROCCAT=m CONFIG_HID_SAITEK=m CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m # CONFIG_SONY_FF is not set CONFIG_HID_SPEEDLINK=m # CONFIG_HID_STEAM is not set CONFIG_HID_STEELSERIES=m CONFIG_HID_SUNPLUS=m CONFIG_HID_RMI=m CONFIG_HID_GREENASIA=m # CONFIG_GREENASIA_FF is not set CONFIG_HID_HYPERV_MOUSE=m CONFIG_HID_SMARTJOYPLUS=m # CONFIG_SMARTJOYPLUS_FF is not set CONFIG_HID_TIVO=m CONFIG_HID_TOPSEED=m CONFIG_HID_THINGM=m CONFIG_HID_THRUSTMASTER=m # CONFIG_THRUSTMASTER_FF is not set # CONFIG_HID_UDRAW_PS3 is not set CONFIG_HID_WACOM=m CONFIG_HID_WIIMOTE=m # CONFIG_HID_XINMO is not set CONFIG_HID_ZEROPLUS=m # CONFIG_ZEROPLUS_FF is not set CONFIG_HID_ZYDACRON=m CONFIG_HID_SENSOR_HUB=m CONFIG_HID_SENSOR_CUSTOM_SENSOR=m CONFIG_HID_ALPS=m # # USB HID support # CONFIG_USB_HID=y CONFIG_HID_PID=y CONFIG_USB_HIDDEV=y # # I2C HID support # CONFIG_I2C_HID=m # # Intel ISH HID support # CONFIG_INTEL_ISH_HID=y CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_SUPPORT=y CONFIG_USB_COMMON=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB=y CONFIG_USB_PCI=y CONFIG_USB_ANNOUNCE_NEW_DEVICES=y # # Miscellaneous USB options # CONFIG_USB_DEFAULT_PERSIST=y # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_OTG is not set # CONFIG_USB_OTG_WHITELIST is not set # CONFIG_USB_OTG_BLACKLIST_HUB is not set CONFIG_USB_LEDS_TRIGGER_USBPORT=m CONFIG_USB_AUTOSUSPEND_DELAY=2 CONFIG_USB_MON=y CONFIG_USB_WUSB=m CONFIG_USB_WUSB_CBAF=m # CONFIG_USB_WUSB_CBAF_DEBUG is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_XHCI_HCD=y # CONFIG_USB_XHCI_DBGCAP is not set CONFIG_USB_XHCI_PCI=y # CONFIG_USB_XHCI_PLATFORM is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_EHCI_PCI=y # CONFIG_USB_EHCI_FSL is not set # CONFIG_USB_EHCI_HCD_PLATFORM is not set # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_FOTG210_HCD is not set # CONFIG_USB_MAX3421_HCD is not set CONFIG_USB_OHCI_HCD=y CONFIG_USB_OHCI_HCD_PCI=y # CONFIG_USB_OHCI_HCD_PLATFORM is not set CONFIG_USB_UHCI_HCD=y # CONFIG_USB_U132_HCD is not set # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_WHCI_HCD is not set CONFIG_USB_HWA_HCD=m # CONFIG_USB_HCD_BCMA is not set # CONFIG_USB_HCD_SSB is not set # CONFIG_USB_HCD_TEST_MODE is not set # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m CONFIG_USB_TMC=m # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_REALTEK=m CONFIG_REALTEK_AUTOPM=y CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m CONFIG_USB_STORAGE_ENE_UB6250=m CONFIG_USB_UAS=m # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m CONFIG_USBIP_CORE=m # CONFIG_USBIP_VHCI_HCD is not set # CONFIG_USBIP_HOST is not set # CONFIG_USBIP_DEBUG is not set # CONFIG_USB_MUSB_HDRC is not set # CONFIG_USB_DWC3 is not set # CONFIG_USB_DWC2 is not set # CONFIG_USB_CHIPIDEA is not set # CONFIG_USB_ISP1760 is not set # # USB port drivers # CONFIG_USB_USS720=m CONFIG_USB_SERIAL=y CONFIG_USB_SERIAL_CONSOLE=y CONFIG_USB_SERIAL_GENERIC=y # CONFIG_USB_SERIAL_SIMPLE is not set CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP210X=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m # CONFIG_USB_SERIAL_F81232 is not set # CONFIG_USB_SERIAL_F8153X is not set CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m # CONFIG_USB_SERIAL_METRO is not set CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7715_PARPORT=y CONFIG_USB_SERIAL_MOS7840=m # CONFIG_USB_SERIAL_MXUPORT is not set CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_QCAUX=m CONFIG_USB_SERIAL_QUALCOMM=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_SAFE=m CONFIG_USB_SERIAL_SAFE_PADDED=y CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_SYMBOL=m # CONFIG_USB_SERIAL_TI is not set CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_WWAN=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_OPTICON=m CONFIG_USB_SERIAL_XSENS_MT=m # CONFIG_USB_SERIAL_WISHBONE is not set CONFIG_USB_SERIAL_SSU100=m CONFIG_USB_SERIAL_QT2=m # CONFIG_USB_SERIAL_UPD78F0730 is not set CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_SEVSEG=m # CONFIG_USB_RIO500 is not set CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set CONFIG_USB_IDMOUSE=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_APPLEDISPLAY=m CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y CONFIG_USB_LD=m # CONFIG_USB_TRANCEVIBRATOR is not set CONFIG_USB_IOWARRIOR=m # CONFIG_USB_TEST is not set # CONFIG_USB_EHSET_TEST_FIXTURE is not set CONFIG_USB_ISIGHTFW=m # CONFIG_USB_YUREX is not set CONFIG_USB_EZUSB_FX2=m # CONFIG_USB_HUB_USB251XB is not set CONFIG_USB_HSIC_USB3503=m # CONFIG_USB_HSIC_USB4604 is not set # CONFIG_USB_LINK_LAYER_TEST is not set # CONFIG_USB_CHAOSKEY is not set CONFIG_USB_ATM=m CONFIG_USB_SPEEDTOUCH=m CONFIG_USB_CXACRU=m CONFIG_USB_UEAGLEATM=m CONFIG_USB_XUSBATM=m # # USB Physical Layer drivers # # CONFIG_NOP_USB_XCEIV is not set # CONFIG_USB_GPIO_VBUS is not set # CONFIG_USB_ISP1301 is not set # CONFIG_USB_GADGET is not set CONFIG_TYPEC=y # CONFIG_TYPEC_TCPM is not set CONFIG_TYPEC_UCSI=y # CONFIG_UCSI_CCG is not set CONFIG_UCSI_ACPI=y # CONFIG_TYPEC_TPS6598X is not set # # USB Type-C Multiplexer/DeMultiplexer Switch support # # CONFIG_TYPEC_MUX_PI3USB30532 is not set # # USB Type-C Alternate Mode drivers # # CONFIG_TYPEC_DP_ALTMODE is not set # CONFIG_USB_ROLE_SWITCH is not set # CONFIG_USB_LED_TRIG is not set # CONFIG_USB_ULPI_BUS is not set CONFIG_UWB=m CONFIG_UWB_HWA=m CONFIG_UWB_WHCI=m CONFIG_UWB_I1480U=m CONFIG_MMC=m CONFIG_MMC_BLOCK=m CONFIG_MMC_BLOCK_MINORS=8 CONFIG_SDIO_UART=m # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # # CONFIG_MMC_DEBUG is not set CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PCI=m CONFIG_MMC_RICOH_MMC=y CONFIG_MMC_SDHCI_ACPI=m CONFIG_MMC_SDHCI_PLTFM=m # CONFIG_MMC_SDHCI_F_SDH30 is not set # CONFIG_MMC_WBSD is not set CONFIG_MMC_TIFM_SD=m # CONFIG_MMC_SPI is not set CONFIG_MMC_CB710=m CONFIG_MMC_VIA_SDMMC=m CONFIG_MMC_VUB300=m CONFIG_MMC_USHC=m # CONFIG_MMC_USDHI6ROL0 is not set CONFIG_MMC_CQHCI=m # CONFIG_MMC_TOSHIBA_PCI is not set # CONFIG_MMC_MTK is not set # CONFIG_MMC_SDHCI_XENON is not set CONFIG_MEMSTICK=m # CONFIG_MEMSTICK_DEBUG is not set # # MemoryStick drivers # # CONFIG_MEMSTICK_UNSAFE_RESUME is not set CONFIG_MSPRO_BLOCK=m # CONFIG_MS_BLOCK is not set # # MemoryStick Host Controller Drivers # CONFIG_MEMSTICK_TIFM_MS=m CONFIG_MEMSTICK_JMICRON_38X=m CONFIG_MEMSTICK_R592=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # CONFIG_LEDS_CLASS_FLASH is not set # CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set # # LED drivers # # CONFIG_LEDS_APU is not set CONFIG_LEDS_LM3530=m # CONFIG_LEDS_LM3642 is not set # CONFIG_LEDS_PCA9532 is not set # CONFIG_LEDS_GPIO is not set CONFIG_LEDS_LP3944=m # CONFIG_LEDS_LP3952 is not set CONFIG_LEDS_LP55XX_COMMON=m CONFIG_LEDS_LP5521=m CONFIG_LEDS_LP5523=m CONFIG_LEDS_LP5562=m # CONFIG_LEDS_LP8501 is not set CONFIG_LEDS_CLEVO_MAIL=m # CONFIG_LEDS_PCA955X is not set # CONFIG_LEDS_PCA963X is not set # CONFIG_LEDS_DAC124S085 is not set # CONFIG_LEDS_PWM is not set # CONFIG_LEDS_BD2802 is not set CONFIG_LEDS_INTEL_SS4200=m CONFIG_LEDS_LT3593=m # CONFIG_LEDS_TCA6507 is not set # CONFIG_LEDS_TLC591XX is not set # CONFIG_LEDS_LM355x is not set # # LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) # CONFIG_LEDS_BLINKM=m # CONFIG_LEDS_MLXCPLD is not set # CONFIG_LEDS_MLXREG is not set # CONFIG_LEDS_USER is not set # CONFIG_LEDS_NIC78BX is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_ONESHOT=m # CONFIG_LEDS_TRIGGER_DISK is not set # CONFIG_LEDS_TRIGGER_MTD is not set CONFIG_LEDS_TRIGGER_HEARTBEAT=m CONFIG_LEDS_TRIGGER_BACKLIGHT=m # CONFIG_LEDS_TRIGGER_CPU is not set # CONFIG_LEDS_TRIGGER_ACTIVITY is not set CONFIG_LEDS_TRIGGER_GPIO=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=m # # iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_NETDEV is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m # CONFIG_ACCESSIBILITY is not set CONFIG_INFINIBAND=m CONFIG_INFINIBAND_USER_MAD=m CONFIG_INFINIBAND_USER_ACCESS=m # CONFIG_INFINIBAND_EXP_LEGACY_VERBS_NEW_UAPI is not set CONFIG_INFINIBAND_USER_MEM=y CONFIG_INFINIBAND_ON_DEMAND_PAGING=y CONFIG_INFINIBAND_ADDR_TRANS=y CONFIG_INFINIBAND_ADDR_TRANS_CONFIGFS=y CONFIG_INFINIBAND_MTHCA=m CONFIG_INFINIBAND_MTHCA_DEBUG=y CONFIG_INFINIBAND_QIB=m CONFIG_INFINIBAND_QIB_DCA=y CONFIG_INFINIBAND_CXGB3=m CONFIG_INFINIBAND_CXGB4=m CONFIG_INFINIBAND_I40IW=m CONFIG_MLX4_INFINIBAND=m CONFIG_MLX5_INFINIBAND=m CONFIG_INFINIBAND_NES=m # CONFIG_INFINIBAND_NES_DEBUG is not set CONFIG_INFINIBAND_OCRDMA=m CONFIG_INFINIBAND_VMWARE_PVRDMA=m CONFIG_INFINIBAND_USNIC=m CONFIG_INFINIBAND_BNXT_RE=m CONFIG_INFINIBAND_HFI1=m # CONFIG_HFI1_DEBUG_SDMA_ORDER is not set # CONFIG_SDMA_VERBOSITY is not set CONFIG_INFINIBAND_QEDR=m CONFIG_INFINIBAND_RDMAVT=m CONFIG_RDMA_RXE=m CONFIG_INFINIBAND_IPOIB=m CONFIG_INFINIBAND_IPOIB_CM=y CONFIG_INFINIBAND_IPOIB_DEBUG=y # CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set CONFIG_INFINIBAND_SRP=m CONFIG_INFINIBAND_SRPT=m CONFIG_INFINIBAND_ISER=m CONFIG_INFINIBAND_ISERT=m CONFIG_INFINIBAND_OPA_VNIC=m CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_GHES=y CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_IE31200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I7CORE=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_EDAC_I7300=m CONFIG_EDAC_SBRIDGE=m CONFIG_EDAC_SKX=m # CONFIG_EDAC_I10NM is not set CONFIG_EDAC_PND2=m CONFIG_RTC_LIB=y CONFIG_RTC_MC146818_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_SYSTOHC is not set # CONFIG_RTC_DEBUG is not set CONFIG_RTC_NVMEM=y # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_ABB5ZES3 is not set # CONFIG_RTC_DRV_ABEOZ9 is not set # CONFIG_RTC_DRV_ABX80X is not set CONFIG_RTC_DRV_DS1307=m # CONFIG_RTC_DRV_DS1307_CENTURY is not set CONFIG_RTC_DRV_DS1374=m # CONFIG_RTC_DRV_DS1374_WDT is not set CONFIG_RTC_DRV_DS1672=m CONFIG_RTC_DRV_MAX6900=m CONFIG_RTC_DRV_RS5C372=m CONFIG_RTC_DRV_ISL1208=m CONFIG_RTC_DRV_ISL12022=m CONFIG_RTC_DRV_X1205=m CONFIG_RTC_DRV_PCF8523=m # CONFIG_RTC_DRV_PCF85063 is not set # CONFIG_RTC_DRV_PCF85363 is not set CONFIG_RTC_DRV_PCF8563=m CONFIG_RTC_DRV_PCF8583=m CONFIG_RTC_DRV_M41T80=m CONFIG_RTC_DRV_M41T80_WDT=y CONFIG_RTC_DRV_BQ32K=m # CONFIG_RTC_DRV_S35390A is not set CONFIG_RTC_DRV_FM3130=m # CONFIG_RTC_DRV_RX8010 is not set CONFIG_RTC_DRV_RX8581=m CONFIG_RTC_DRV_RX8025=m CONFIG_RTC_DRV_EM3027=m # CONFIG_RTC_DRV_RV3028 is not set # CONFIG_RTC_DRV_RV8803 is not set # CONFIG_RTC_DRV_SD3078 is not set # # SPI RTC drivers # # CONFIG_RTC_DRV_M41T93 is not set # CONFIG_RTC_DRV_M41T94 is not set # CONFIG_RTC_DRV_DS1302 is not set # CONFIG_RTC_DRV_DS1305 is not set # CONFIG_RTC_DRV_DS1343 is not set # CONFIG_RTC_DRV_DS1347 is not set # CONFIG_RTC_DRV_DS1390 is not set # CONFIG_RTC_DRV_MAX6916 is not set # CONFIG_RTC_DRV_R9701 is not set CONFIG_RTC_DRV_RX4581=m # CONFIG_RTC_DRV_RX6110 is not set # CONFIG_RTC_DRV_RS5C348 is not set # CONFIG_RTC_DRV_MAX6902 is not set # CONFIG_RTC_DRV_PCF2123 is not set # CONFIG_RTC_DRV_MCP795 is not set CONFIG_RTC_I2C_AND_SPI=y # # SPI and I2C RTC drivers # CONFIG_RTC_DRV_DS3232=m CONFIG_RTC_DRV_DS3232_HWMON=y # CONFIG_RTC_DRV_PCF2127 is not set CONFIG_RTC_DRV_RV3029C2=m CONFIG_RTC_DRV_RV3029_HWMON=y # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y CONFIG_RTC_DRV_DS1286=m CONFIG_RTC_DRV_DS1511=m CONFIG_RTC_DRV_DS1553=m # CONFIG_RTC_DRV_DS1685_FAMILY is not set CONFIG_RTC_DRV_DS1742=m CONFIG_RTC_DRV_DS2404=m CONFIG_RTC_DRV_STK17TA8=m # CONFIG_RTC_DRV_M48T86 is not set CONFIG_RTC_DRV_M48T35=m CONFIG_RTC_DRV_M48T59=m CONFIG_RTC_DRV_MSM6242=m CONFIG_RTC_DRV_BQ4802=m CONFIG_RTC_DRV_RP5C01=m CONFIG_RTC_DRV_V3020=m # # on-CPU RTC drivers # # CONFIG_RTC_DRV_FTRTC010 is not set # # HID Sensor RTC drivers # # CONFIG_RTC_DRV_HID_SENSOR_TIME is not set CONFIG_DMADEVICES=y # CONFIG_DMADEVICES_DEBUG is not set # # DMA Devices # CONFIG_DMA_ENGINE=y CONFIG_DMA_VIRTUAL_CHANNELS=y CONFIG_DMA_ACPI=y # CONFIG_ALTERA_MSGDMA is not set # CONFIG_INTEL_IDMA64 is not set CONFIG_INTEL_IOATDMA=m # CONFIG_QCOM_HIDMA_MGMT is not set # CONFIG_QCOM_HIDMA is not set CONFIG_DW_DMAC_CORE=y CONFIG_DW_DMAC=m CONFIG_DW_DMAC_PCI=y CONFIG_HSU_DMA=y # # DMA Clients # CONFIG_ASYNC_TX_DMA=y # CONFIG_DMATEST is not set CONFIG_DMA_ENGINE_RAID=y # # DMABUF options # CONFIG_SYNC_FILE=y CONFIG_SW_SYNC=y # CONFIG_UDMABUF is not set CONFIG_DCA=m CONFIG_AUXDISPLAY=y # CONFIG_HD44780 is not set CONFIG_KS0108=m CONFIG_KS0108_PORT=0x378 CONFIG_KS0108_DELAY=2 CONFIG_CFAG12864B=m CONFIG_CFAG12864B_RATE=20 # CONFIG_IMG_ASCII_LCD is not set # CONFIG_PARPORT_PANEL is not set # CONFIG_CHARLCD_BL_OFF is not set # CONFIG_CHARLCD_BL_ON is not set CONFIG_CHARLCD_BL_FLASH=y # CONFIG_PANEL is not set CONFIG_UIO=m CONFIG_UIO_CIF=m CONFIG_UIO_PDRV_GENIRQ=m # CONFIG_UIO_DMEM_GENIRQ is not set CONFIG_UIO_AEC=m CONFIG_UIO_SERCOS3=m CONFIG_UIO_PCI_GENERIC=m # CONFIG_UIO_NETX is not set # CONFIG_UIO_PRUSS is not set # CONFIG_UIO_MF624 is not set CONFIG_UIO_HV_GENERIC=m CONFIG_VFIO_IOMMU_TYPE1=m CONFIG_VFIO_VIRQFD=m CONFIG_VFIO=m CONFIG_VFIO_NOIOMMU=y CONFIG_VFIO_PCI=m # CONFIG_VFIO_PCI_VGA is not set CONFIG_VFIO_PCI_MMAP=y CONFIG_VFIO_PCI_INTX=y # CONFIG_VFIO_PCI_IGD is not set CONFIG_VFIO_MDEV=m CONFIG_VFIO_MDEV_DEVICE=m CONFIG_IRQ_BYPASS_MANAGER=m # CONFIG_VIRT_DRIVERS is not set CONFIG_VIRTIO=y CONFIG_VIRTIO_MENU=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_INPUT=m # CONFIG_VIRTIO_MMIO is not set # # Microsoft Hyper-V guest support # CONFIG_HYPERV=m CONFIG_HYPERV_TSCPAGE=y CONFIG_HYPERV_UTILS=m CONFIG_HYPERV_BALLOON=m # # Xen driver support # CONFIG_XEN_BALLOON=y # CONFIG_XEN_SELFBALLOONING is not set # CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set CONFIG_XEN_SCRUB_PAGES_DEFAULT=y CONFIG_XEN_DEV_EVTCHN=m # CONFIG_XEN_BACKEND is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y # CONFIG_XEN_GNTDEV is not set # CONFIG_XEN_GRANT_DEV_ALLOC is not set # CONFIG_XEN_GRANT_DMA_ALLOC is not set CONFIG_SWIOTLB_XEN=y CONFIG_XEN_TMEM=m # CONFIG_XEN_PVCALLS_FRONTEND is not set CONFIG_XEN_PRIVCMD=m CONFIG_XEN_HAVE_PVMMU=y CONFIG_XEN_EFI=y CONFIG_XEN_AUTO_XLATE=y CONFIG_XEN_ACPI=y CONFIG_XEN_HAVE_VPMU=y CONFIG_STAGING=y # CONFIG_PRISM2_USB is not set # CONFIG_COMEDI is not set # CONFIG_RTL8192U is not set CONFIG_RTLLIB=m CONFIG_RTLLIB_CRYPTO_CCMP=m CONFIG_RTLLIB_CRYPTO_TKIP=m CONFIG_RTLLIB_CRYPTO_WEP=m CONFIG_RTL8192E=m # CONFIG_RTL8723BS is not set CONFIG_R8712U=m # CONFIG_R8188EU is not set # CONFIG_R8822BE is not set # CONFIG_RTS5208 is not set # CONFIG_VT6655 is not set # CONFIG_VT6656 is not set # # IIO staging drivers # # # Accelerometers # # CONFIG_ADIS16203 is not set # CONFIG_ADIS16240 is not set # # Analog to digital converters # # CONFIG_AD7780 is not set # CONFIG_AD7816 is not set # CONFIG_AD7192 is not set # CONFIG_AD7280 is not set # # Analog digital bi-direction converters # # CONFIG_ADT7316 is not set # # Capacitance to digital converters # # CONFIG_AD7150 is not set # CONFIG_AD7746 is not set # # Direct Digital Synthesis # # CONFIG_AD9832 is not set # CONFIG_AD9834 is not set # # Network Analyzer, Impedance Converters # # CONFIG_AD5933 is not set # # Active energy metering IC # # CONFIG_ADE7854 is not set # # Resolver to digital converters # # CONFIG_AD2S1210 is not set # CONFIG_FB_SM750 is not set # # Speakup console speech # # CONFIG_SPEAKUP is not set # CONFIG_STAGING_MEDIA is not set # # Android # # CONFIG_LTE_GDM724X is not set CONFIG_FIREWIRE_SERIAL=m CONFIG_FWTTY_MAX_TOTAL_PORTS=64 CONFIG_FWTTY_MAX_CARD_PORTS=32 # CONFIG_GS_FPGABOOT is not set # CONFIG_UNISYSSPAR is not set # CONFIG_FB_TFT is not set # CONFIG_WILC1000_SDIO is not set # CONFIG_WILC1000_SPI is not set # CONFIG_MOST is not set # CONFIG_KS7010 is not set # CONFIG_GREYBUS is not set # CONFIG_DRM_VBOXVIDEO is not set # CONFIG_PI433 is not set # # Gasket devices # # CONFIG_STAGING_GASKET_FRAMEWORK is not set # CONFIG_EROFS_FS is not set CONFIG_X86_PLATFORM_DEVICES=y CONFIG_ACER_WMI=m # CONFIG_ACER_WIRELESS is not set CONFIG_ACERHDF=m # CONFIG_ALIENWARE_WMI is not set CONFIG_ASUS_LAPTOP=m CONFIG_DCDBAS=m CONFIG_DELL_SMBIOS=m CONFIG_DELL_SMBIOS_WMI=y CONFIG_DELL_SMBIOS_SMM=y CONFIG_DELL_LAPTOP=m CONFIG_DELL_WMI=m CONFIG_DELL_WMI_DESCRIPTOR=m CONFIG_DELL_WMI_AIO=m # CONFIG_DELL_WMI_LED is not set CONFIG_DELL_SMO8800=m CONFIG_DELL_RBTN=m CONFIG_DELL_RBU=m CONFIG_FUJITSU_LAPTOP=m CONFIG_FUJITSU_TABLET=m CONFIG_AMILO_RFKILL=m # CONFIG_GPD_POCKET_FAN is not set CONFIG_HP_ACCEL=m CONFIG_HP_WIRELESS=m CONFIG_HP_WMI=m # CONFIG_LG_LAPTOP is not set CONFIG_MSI_LAPTOP=m CONFIG_PANASONIC_LAPTOP=m CONFIG_COMPAL_LAPTOP=m CONFIG_SONY_LAPTOP=m CONFIG_SONYPI_COMPAT=y CONFIG_IDEAPAD_LAPTOP=m # CONFIG_SURFACE3_WMI is not set CONFIG_THINKPAD_ACPI=m CONFIG_THINKPAD_ACPI_ALSA_SUPPORT=y # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_SENSORS_HDAPS=m # CONFIG_INTEL_MENLOW is not set CONFIG_EEEPC_LAPTOP=m CONFIG_ASUS_WMI=m CONFIG_ASUS_NB_WMI=m CONFIG_EEEPC_WMI=m # CONFIG_ASUS_WIRELESS is not set CONFIG_ACPI_WMI=m CONFIG_WMI_BMOF=m CONFIG_INTEL_WMI_THUNDERBOLT=m CONFIG_MSI_WMI=m # CONFIG_PEAQ_WMI is not set CONFIG_TOPSTAR_LAPTOP=m CONFIG_ACPI_TOSHIBA=m CONFIG_TOSHIBA_BT_RFKILL=m # CONFIG_TOSHIBA_HAPS is not set # CONFIG_TOSHIBA_WMI is not set CONFIG_ACPI_CMPC=m # CONFIG_INTEL_INT0002_VGPIO is not set CONFIG_INTEL_HID_EVENT=m CONFIG_INTEL_VBTN=m CONFIG_INTEL_IPS=m CONFIG_INTEL_PMC_CORE=m # CONFIG_IBM_RTL is not set CONFIG_SAMSUNG_LAPTOP=m CONFIG_MXM_WMI=m CONFIG_INTEL_OAKTRAIL=m CONFIG_SAMSUNG_Q10=m CONFIG_APPLE_GMUX=m # CONFIG_INTEL_RST is not set # CONFIG_INTEL_SMARTCONNECT is not set # CONFIG_INTEL_PMC_IPC is not set # CONFIG_SURFACE_PRO3_BUTTON is not set # CONFIG_INTEL_PUNIT_IPC is not set # CONFIG_MLX_PLATFORM is not set # CONFIG_INTEL_TURBO_MAX_3 is not set # CONFIG_I2C_MULTI_INSTANTIATE is not set # CONFIG_INTEL_ATOMISP2_PM is not set # CONFIG_HUAWEI_WMI is not set # CONFIG_PCENGINES_APU2 is not set CONFIG_PMC_ATOM=y # CONFIG_CHROME_PLATFORMS is not set # CONFIG_MELLANOX_PLATFORM is not set CONFIG_CLKDEV_LOOKUP=y CONFIG_HAVE_CLK_PREPARE=y CONFIG_COMMON_CLK=y # # Common Clock Framework # # CONFIG_COMMON_CLK_MAX9485 is not set # CONFIG_COMMON_CLK_SI5351 is not set # CONFIG_COMMON_CLK_SI544 is not set # CONFIG_COMMON_CLK_CDCE706 is not set # CONFIG_COMMON_CLK_CS2000_CP is not set # CONFIG_COMMON_CLK_PWM is not set # CONFIG_HWSPINLOCK is not set # # Clock Source drivers # CONFIG_CLKEVT_I8253=y CONFIG_I8253_LOCK=y CONFIG_CLKBLD_I8253=y CONFIG_MAILBOX=y CONFIG_PCC=y # CONFIG_ALTERA_MBOX is not set CONFIG_IOMMU_IOVA=y CONFIG_IOMMU_API=y CONFIG_IOMMU_SUPPORT=y # # Generic IOMMU Pagetable Support # # CONFIG_IOMMU_DEBUGFS is not set # CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set CONFIG_AMD_IOMMU=y CONFIG_AMD_IOMMU_V2=m CONFIG_DMAR_TABLE=y CONFIG_INTEL_IOMMU=y # CONFIG_INTEL_IOMMU_SVM is not set # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set CONFIG_INTEL_IOMMU_FLOPPY_WA=y CONFIG_IRQ_REMAP=y CONFIG_HYPERV_IOMMU=y # # Remoteproc drivers # # CONFIG_REMOTEPROC is not set # # Rpmsg drivers # # CONFIG_RPMSG_QCOM_GLINK_RPM is not set # CONFIG_RPMSG_VIRTIO is not set # CONFIG_SOUNDWIRE is not set # # SOC (System On Chip) specific Drivers # # # Amlogic SoC drivers # # # Broadcom SoC drivers # # # NXP/Freescale QorIQ SoC drivers # # # i.MX SoC drivers # # # Qualcomm SoC drivers # # CONFIG_SOC_TI is not set # # Xilinx SoC drivers # # CONFIG_XILINX_VCU is not set CONFIG_PM_DEVFREQ=y # # DEVFREQ Governors # CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=m # CONFIG_DEVFREQ_GOV_PERFORMANCE is not set # CONFIG_DEVFREQ_GOV_POWERSAVE is not set # CONFIG_DEVFREQ_GOV_USERSPACE is not set # CONFIG_DEVFREQ_GOV_PASSIVE is not set # # DEVFREQ Drivers # # CONFIG_PM_DEVFREQ_EVENT is not set # CONFIG_EXTCON is not set # CONFIG_MEMORY is not set CONFIG_IIO=y CONFIG_IIO_BUFFER=y CONFIG_IIO_BUFFER_CB=y # CONFIG_IIO_BUFFER_HW_CONSUMER is not set CONFIG_IIO_KFIFO_BUF=y CONFIG_IIO_TRIGGERED_BUFFER=m # CONFIG_IIO_CONFIGFS is not set CONFIG_IIO_TRIGGER=y CONFIG_IIO_CONSUMERS_PER_TRIGGER=2 # CONFIG_IIO_SW_DEVICE is not set # CONFIG_IIO_SW_TRIGGER is not set # # Accelerometers # # CONFIG_ADIS16201 is not set # CONFIG_ADIS16209 is not set # CONFIG_ADXL345_I2C is not set # CONFIG_ADXL345_SPI is not set # CONFIG_ADXL372_SPI is not set # CONFIG_ADXL372_I2C is not set # CONFIG_BMA180 is not set # CONFIG_BMA220 is not set # CONFIG_BMC150_ACCEL is not set # CONFIG_DA280 is not set # CONFIG_DA311 is not set # CONFIG_DMARD09 is not set # CONFIG_DMARD10 is not set CONFIG_HID_SENSOR_ACCEL_3D=m # CONFIG_IIO_CROS_EC_ACCEL_LEGACY is not set # CONFIG_IIO_ST_ACCEL_3AXIS is not set # CONFIG_KXSD9 is not set # CONFIG_KXCJK1013 is not set # CONFIG_MC3230 is not set # CONFIG_MMA7455_I2C is not set # CONFIG_MMA7455_SPI is not set # CONFIG_MMA7660 is not set # CONFIG_MMA8452 is not set # CONFIG_MMA9551 is not set # CONFIG_MMA9553 is not set # CONFIG_MXC4005 is not set # CONFIG_MXC6255 is not set # CONFIG_SCA3000 is not set # CONFIG_STK8312 is not set # CONFIG_STK8BA50 is not set # # Analog to digital converters # # CONFIG_AD7124 is not set # CONFIG_AD7266 is not set # CONFIG_AD7291 is not set # CONFIG_AD7298 is not set # CONFIG_AD7476 is not set # CONFIG_AD7606_IFACE_PARALLEL is not set # CONFIG_AD7606_IFACE_SPI is not set # CONFIG_AD7766 is not set # CONFIG_AD7768_1 is not set # CONFIG_AD7791 is not set # CONFIG_AD7793 is not set # CONFIG_AD7887 is not set # CONFIG_AD7923 is not set # CONFIG_AD7949 is not set # CONFIG_AD799X is not set # CONFIG_HI8435 is not set # CONFIG_HX711 is not set # CONFIG_INA2XX_ADC is not set # CONFIG_LTC2471 is not set # CONFIG_LTC2485 is not set # CONFIG_LTC2497 is not set # CONFIG_MAX1027 is not set # CONFIG_MAX11100 is not set # CONFIG_MAX1118 is not set # CONFIG_MAX1363 is not set # CONFIG_MAX9611 is not set # CONFIG_MCP320X is not set # CONFIG_MCP3422 is not set # CONFIG_MCP3911 is not set # CONFIG_NAU7802 is not set # CONFIG_TI_ADC081C is not set # CONFIG_TI_ADC0832 is not set # CONFIG_TI_ADC084S021 is not set # CONFIG_TI_ADC12138 is not set # CONFIG_TI_ADC108S102 is not set # CONFIG_TI_ADC128S052 is not set # CONFIG_TI_ADC161S626 is not set # CONFIG_TI_ADS1015 is not set # CONFIG_TI_ADS7950 is not set # CONFIG_TI_TLC4541 is not set # CONFIG_VIPERBOARD_ADC is not set # # Analog Front Ends # # # Amplifiers # # CONFIG_AD8366 is not set # # Chemical Sensors # # CONFIG_ATLAS_PH_SENSOR is not set # CONFIG_BME680 is not set # CONFIG_CCS811 is not set # CONFIG_IAQCORE is not set # CONFIG_SPS30 is not set # CONFIG_VZ89X is not set # # Hid Sensor IIO Common # CONFIG_HID_SENSOR_IIO_COMMON=m CONFIG_HID_SENSOR_IIO_TRIGGER=m # # SSP Sensor Common # # CONFIG_IIO_SSP_SENSORHUB is not set # # Counters # # # Digital to analog converters # # CONFIG_AD5064 is not set # CONFIG_AD5360 is not set # CONFIG_AD5380 is not set # CONFIG_AD5421 is not set # CONFIG_AD5446 is not set # CONFIG_AD5449 is not set # CONFIG_AD5592R is not set # CONFIG_AD5593R is not set # CONFIG_AD5504 is not set # CONFIG_AD5624R_SPI is not set # CONFIG_LTC1660 is not set # CONFIG_LTC2632 is not set # CONFIG_AD5686_SPI is not set # CONFIG_AD5696_I2C is not set # CONFIG_AD5755 is not set # CONFIG_AD5758 is not set # CONFIG_AD5761 is not set # CONFIG_AD5764 is not set # CONFIG_AD5791 is not set # CONFIG_AD7303 is not set # CONFIG_AD8801 is not set # CONFIG_DS4424 is not set # CONFIG_M62332 is not set # CONFIG_MAX517 is not set # CONFIG_MCP4725 is not set # CONFIG_MCP4922 is not set # CONFIG_TI_DAC082S085 is not set # CONFIG_TI_DAC5571 is not set # CONFIG_TI_DAC7311 is not set # CONFIG_TI_DAC7612 is not set # # IIO dummy driver # # # Frequency Synthesizers DDS/PLL # # # Clock Generator/Distribution # # CONFIG_AD9523 is not set # # Phase-Locked Loop (PLL) frequency synthesizers # # CONFIG_ADF4350 is not set # # Digital gyroscope sensors # # CONFIG_ADIS16080 is not set # CONFIG_ADIS16130 is not set # CONFIG_ADIS16136 is not set # CONFIG_ADIS16260 is not set # CONFIG_ADXRS450 is not set # CONFIG_BMG160 is not set CONFIG_HID_SENSOR_GYRO_3D=m # CONFIG_MPU3050_I2C is not set # CONFIG_IIO_ST_GYRO_3AXIS is not set # CONFIG_ITG3200 is not set # # Health Sensors # # # Heart Rate Monitors # # CONFIG_AFE4403 is not set # CONFIG_AFE4404 is not set # CONFIG_MAX30100 is not set # CONFIG_MAX30102 is not set # # Humidity sensors # # CONFIG_AM2315 is not set # CONFIG_DHT11 is not set # CONFIG_HDC100X is not set # CONFIG_HID_SENSOR_HUMIDITY is not set # CONFIG_HTS221 is not set # CONFIG_HTU21 is not set # CONFIG_SI7005 is not set # CONFIG_SI7020 is not set # # Inertial measurement units # # CONFIG_ADIS16400 is not set # CONFIG_ADIS16480 is not set # CONFIG_BMI160_I2C is not set # CONFIG_BMI160_SPI is not set # CONFIG_KMX61 is not set # CONFIG_INV_MPU6050_I2C is not set # CONFIG_INV_MPU6050_SPI is not set # CONFIG_IIO_ST_LSM6DSX is not set # # Light sensors # # CONFIG_ACPI_ALS is not set # CONFIG_ADJD_S311 is not set # CONFIG_AL3320A is not set # CONFIG_APDS9300 is not set # CONFIG_APDS9960 is not set # CONFIG_BH1750 is not set # CONFIG_BH1780 is not set # CONFIG_CM32181 is not set # CONFIG_CM3232 is not set # CONFIG_CM3323 is not set # CONFIG_CM36651 is not set # CONFIG_GP2AP020A00F is not set # CONFIG_SENSORS_ISL29018 is not set # CONFIG_SENSORS_ISL29028 is not set # CONFIG_ISL29125 is not set CONFIG_HID_SENSOR_ALS=m CONFIG_HID_SENSOR_PROX=m # CONFIG_JSA1212 is not set # CONFIG_RPR0521 is not set # CONFIG_LTR501 is not set # CONFIG_LV0104CS is not set # CONFIG_MAX44000 is not set # CONFIG_MAX44009 is not set # CONFIG_OPT3001 is not set # CONFIG_PA12203001 is not set # CONFIG_SI1133 is not set # CONFIG_SI1145 is not set # CONFIG_STK3310 is not set # CONFIG_ST_UVIS25 is not set # CONFIG_TCS3414 is not set # CONFIG_TCS3472 is not set # CONFIG_SENSORS_TSL2563 is not set # CONFIG_TSL2583 is not set # CONFIG_TSL2772 is not set # CONFIG_TSL4531 is not set # CONFIG_US5182D is not set # CONFIG_VCNL4000 is not set # CONFIG_VCNL4035 is not set # CONFIG_VEML6070 is not set # CONFIG_VL6180 is not set # CONFIG_ZOPT2201 is not set # # Magnetometer sensors # # CONFIG_AK8975 is not set # CONFIG_AK09911 is not set # CONFIG_BMC150_MAGN_I2C is not set # CONFIG_BMC150_MAGN_SPI is not set # CONFIG_MAG3110 is not set CONFIG_HID_SENSOR_MAGNETOMETER_3D=m # CONFIG_MMC35240 is not set # CONFIG_IIO_ST_MAGN_3AXIS is not set # CONFIG_SENSORS_HMC5843_I2C is not set # CONFIG_SENSORS_HMC5843_SPI is not set # CONFIG_SENSORS_RM3100_I2C is not set # CONFIG_SENSORS_RM3100_SPI is not set # # Multiplexers # # # Inclinometer sensors # CONFIG_HID_SENSOR_INCLINOMETER_3D=m CONFIG_HID_SENSOR_DEVICE_ROTATION=m # # Triggers - standalone # # CONFIG_IIO_INTERRUPT_TRIGGER is not set # CONFIG_IIO_SYSFS_TRIGGER is not set # # Digital potentiometers # # CONFIG_AD5272 is not set # CONFIG_DS1803 is not set # CONFIG_MAX5481 is not set # CONFIG_MAX5487 is not set # CONFIG_MCP4018 is not set # CONFIG_MCP4131 is not set # CONFIG_MCP4531 is not set # CONFIG_MCP41010 is not set # CONFIG_TPL0102 is not set # # Digital potentiostats # # CONFIG_LMP91000 is not set # # Pressure sensors # # CONFIG_ABP060MG is not set # CONFIG_BMP280 is not set CONFIG_HID_SENSOR_PRESS=m # CONFIG_HP03 is not set # CONFIG_MPL115_I2C is not set # CONFIG_MPL115_SPI is not set # CONFIG_MPL3115 is not set # CONFIG_MS5611 is not set # CONFIG_MS5637 is not set # CONFIG_IIO_ST_PRESS is not set # CONFIG_T5403 is not set # CONFIG_HP206C is not set # CONFIG_ZPA2326 is not set # # Lightning sensors # # CONFIG_AS3935 is not set # # Proximity and distance sensors # # CONFIG_ISL29501 is not set # CONFIG_LIDAR_LITE_V2 is not set # CONFIG_RFD77402 is not set # CONFIG_SRF04 is not set # CONFIG_SX9500 is not set # CONFIG_SRF08 is not set # CONFIG_VL53L0X_I2C is not set # # Resolver to digital converters # # CONFIG_AD2S90 is not set # CONFIG_AD2S1200 is not set # # Temperature sensors # # CONFIG_MAXIM_THERMOCOUPLE is not set # CONFIG_HID_SENSOR_TEMP is not set # CONFIG_MLX90614 is not set # CONFIG_MLX90632 is not set # CONFIG_TMP006 is not set # CONFIG_TMP007 is not set # CONFIG_TSYS01 is not set # CONFIG_TSYS02D is not set CONFIG_NTB=m CONFIG_NTB_AMD=m # CONFIG_NTB_IDT is not set # CONFIG_NTB_INTEL is not set # CONFIG_NTB_SWITCHTEC is not set # CONFIG_NTB_PINGPONG is not set # CONFIG_NTB_TOOL is not set CONFIG_NTB_PERF=m CONFIG_NTB_TRANSPORT=m # CONFIG_VME_BUS is not set CONFIG_PWM=y CONFIG_PWM_SYSFS=y # CONFIG_PWM_LPSS_PCI is not set # CONFIG_PWM_LPSS_PLATFORM is not set # CONFIG_PWM_PCA9685 is not set # # IRQ chip support # CONFIG_ARM_GIC_MAX_NR=1 # CONFIG_IPACK_BUS is not set # CONFIG_RESET_CONTROLLER is not set # CONFIG_FMC is not set # # PHY Subsystem # CONFIG_GENERIC_PHY=y # CONFIG_BCM_KONA_USB2_PHY is not set # CONFIG_PHY_PXA_28NM_HSIC is not set # CONFIG_PHY_PXA_28NM_USB2 is not set # CONFIG_PHY_CPCAP_USB is not set CONFIG_POWERCAP=y CONFIG_INTEL_RAPL=m # CONFIG_IDLE_INJECT is not set # CONFIG_MCB is not set # # Performance monitor support # CONFIG_RAS=y # CONFIG_RAS_CEC is not set CONFIG_THUNDERBOLT=y # # Android # # CONFIG_ANDROID is not set CONFIG_LIBNVDIMM=m CONFIG_BLK_DEV_PMEM=m CONFIG_ND_BLK=m CONFIG_ND_CLAIM=y CONFIG_ND_BTT=m CONFIG_BTT=y CONFIG_ND_PFN=m CONFIG_NVDIMM_PFN=y CONFIG_NVDIMM_DAX=y CONFIG_NVDIMM_KEYS=y CONFIG_DAX_DRIVER=y CONFIG_DAX=y CONFIG_DEV_DAX=m CONFIG_DEV_DAX_PMEM=m CONFIG_DEV_DAX_KMEM=m CONFIG_DEV_DAX_PMEM_COMPAT=m CONFIG_NVMEM=y # # HW tracing support # # CONFIG_STM is not set # CONFIG_INTEL_TH is not set # CONFIG_FPGA is not set CONFIG_PM_OPP=y # CONFIG_UNISYS_VISORBUS is not set # CONFIG_SIOX is not set # CONFIG_SLIMBUS is not set # CONFIG_INTERCONNECT is not set # # File systems # CONFIG_DCACHE_WORD_ACCESS=y CONFIG_VALIDATE_FS_PARSER=y CONFIG_FS_IOMAP=y # CONFIG_EXT2_FS is not set # CONFIG_EXT3_FS is not set CONFIG_EXT4_FS=m CONFIG_EXT4_USE_FOR_EXT2=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set CONFIG_JBD2=m # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=m # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_XFS_FS=m CONFIG_XFS_QUOTA=y CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y CONFIG_XFS_ONLINE_SCRUB=y CONFIG_XFS_ONLINE_REPAIR=y CONFIG_XFS_DEBUG=y CONFIG_XFS_ASSERT_FATAL=y CONFIG_GFS2_FS=m CONFIG_GFS2_FS_LOCKING_DLM=y CONFIG_OCFS2_FS=m CONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m CONFIG_OCFS2_FS_STATS=y CONFIG_OCFS2_DEBUG_MASKLOG=y # CONFIG_OCFS2_DEBUG_FS is not set CONFIG_BTRFS_FS=m CONFIG_BTRFS_FS_POSIX_ACL=y # CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set # CONFIG_BTRFS_DEBUG is not set # CONFIG_BTRFS_ASSERT is not set # CONFIG_BTRFS_FS_REF_VERIFY is not set # CONFIG_NILFS2_FS is not set CONFIG_F2FS_FS=m CONFIG_F2FS_STAT_FS=y CONFIG_F2FS_FS_XATTR=y CONFIG_F2FS_FS_POSIX_ACL=y # CONFIG_F2FS_FS_SECURITY is not set # CONFIG_F2FS_CHECK_FS is not set # CONFIG_F2FS_IO_TRACE is not set # CONFIG_F2FS_FAULT_INJECTION is not set CONFIG_FS_DAX=y CONFIG_FS_DAX_PMD=y CONFIG_FS_POSIX_ACL=y CONFIG_EXPORTFS=y CONFIG_EXPORTFS_BLOCK_OPS=y CONFIG_FILE_LOCKING=y CONFIG_MANDATORY_FILE_LOCKING=y CONFIG_FS_ENCRYPTION=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y CONFIG_PRINT_QUOTA_WARNING=y # CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=y # CONFIG_QFMT_V1 is not set CONFIG_QFMT_V2=y CONFIG_QUOTACTL=y CONFIG_QUOTACTL_COMPAT=y CONFIG_AUTOFS4_FS=y CONFIG_AUTOFS_FS=y CONFIG_FUSE_FS=m CONFIG_CUSE=m CONFIG_OVERLAY_FS=m # CONFIG_OVERLAY_FS_REDIRECT_DIR is not set # CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set # CONFIG_OVERLAY_FS_INDEX is not set # CONFIG_OVERLAY_FS_XINO_AUTO is not set # CONFIG_OVERLAY_FS_METACOPY is not set # # Caches # CONFIG_FSCACHE=m CONFIG_FSCACHE_STATS=y # CONFIG_FSCACHE_HISTOGRAM is not set # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set CONFIG_CACHEFILES=m # CONFIG_CACHEFILES_DEBUG is not set # CONFIG_CACHEFILES_HISTOGRAM is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="ascii" # CONFIG_FAT_DEFAULT_UTF8 is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_VMCORE=y # CONFIG_PROC_VMCORE_DEVICE_DUMP is not set CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_CHILDREN=y CONFIG_KERNFS=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_MEMFD_CREATE=y CONFIG_ARCH_HAS_GIGANTIC_PAGE=y CONFIG_CONFIGFS_FS=y CONFIG_EFIVAR_FS=y CONFIG_MISC_FILESYSTEMS=y # CONFIG_ORANGEFS_FS is not set # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_ECRYPT_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_JFFS2_FS is not set # CONFIG_UBIFS_FS is not set CONFIG_CRAMFS=m CONFIG_CRAMFS_BLOCKDEV=y # CONFIG_CRAMFS_MTD is not set CONFIG_SQUASHFS=m CONFIG_SQUASHFS_FILE_CACHE=y # CONFIG_SQUASHFS_FILE_DIRECT is not set CONFIG_SQUASHFS_DECOMP_SINGLE=y # CONFIG_SQUASHFS_DECOMP_MULTI is not set # CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU is not set CONFIG_SQUASHFS_XATTR=y CONFIG_SQUASHFS_ZLIB=y # CONFIG_SQUASHFS_LZ4 is not set CONFIG_SQUASHFS_LZO=y CONFIG_SQUASHFS_XZ=y # CONFIG_SQUASHFS_ZSTD is not set # CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 # CONFIG_VXFS_FS is not set CONFIG_MINIX_FS=m # CONFIG_OMFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_QNX6FS_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_PSTORE=y CONFIG_PSTORE_DEFLATE_COMPRESS=y # CONFIG_PSTORE_LZO_COMPRESS is not set # CONFIG_PSTORE_LZ4_COMPRESS is not set # CONFIG_PSTORE_LZ4HC_COMPRESS is not set # CONFIG_PSTORE_842_COMPRESS is not set # CONFIG_PSTORE_ZSTD_COMPRESS is not set CONFIG_PSTORE_COMPRESS=y CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT=y CONFIG_PSTORE_COMPRESS_DEFAULT="deflate" CONFIG_PSTORE_CONSOLE=y CONFIG_PSTORE_PMSG=y # CONFIG_PSTORE_FTRACE is not set CONFIG_PSTORE_RAM=m # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y # CONFIG_NFS_V2 is not set CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=m # CONFIG_NFS_SWAP is not set CONFIG_NFS_V4_1=y CONFIG_NFS_V4_2=y CONFIG_PNFS_FILE_LAYOUT=m CONFIG_PNFS_BLOCK=m CONFIG_PNFS_FLEXFILE_LAYOUT=m CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org" # CONFIG_NFS_V4_1_MIGRATION is not set CONFIG_NFS_V4_SECURITY_LABEL=y CONFIG_ROOT_NFS=y # CONFIG_NFS_USE_LEGACY_DNS is not set CONFIG_NFS_USE_KERNEL_DNS=y CONFIG_NFS_DEBUG=y CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_NFSD_PNFS=y # CONFIG_NFSD_BLOCKLAYOUT is not set CONFIG_NFSD_SCSILAYOUT=y # CONFIG_NFSD_FLEXFILELAYOUT is not set CONFIG_NFSD_V4_SECURITY_LABEL=y # CONFIG_NFSD_FAULT_INJECTION is not set CONFIG_GRACE_PERIOD=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=m CONFIG_SUNRPC_BACKCHANNEL=y CONFIG_RPCSEC_GSS_KRB5=m # CONFIG_CONFIG_SUNRPC_DISABLE_INSECURE_ENCTYPES is not set CONFIG_SUNRPC_DEBUG=y CONFIG_SUNRPC_XPRT_RDMA=m CONFIG_CEPH_FS=m # CONFIG_CEPH_FSCACHE is not set CONFIG_CEPH_FS_POSIX_ACL=y CONFIG_CIFS=m # CONFIG_CIFS_STATS2 is not set CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y CONFIG_CIFS_ACL=y CONFIG_CIFS_DEBUG=y # CONFIG_CIFS_DEBUG2 is not set # CONFIG_CIFS_DEBUG_DUMP_KEYS is not set CONFIG_CIFS_DFS_UPCALL=y # CONFIG_CIFS_SMB_DIRECT is not set # CONFIG_CIFS_FSCACHE is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set CONFIG_9P_FS=y CONFIG_9P_FS_POSIX_ACL=y # CONFIG_9P_FS_SECURITY is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="utf8" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_MAC_ROMAN=m CONFIG_NLS_MAC_CELTIC=m CONFIG_NLS_MAC_CENTEURO=m CONFIG_NLS_MAC_CROATIAN=m CONFIG_NLS_MAC_CYRILLIC=m CONFIG_NLS_MAC_GAELIC=m CONFIG_NLS_MAC_GREEK=m CONFIG_NLS_MAC_ICELAND=m CONFIG_NLS_MAC_INUIT=m CONFIG_NLS_MAC_ROMANIAN=m CONFIG_NLS_MAC_TURKISH=m CONFIG_NLS_UTF8=m CONFIG_DLM=m CONFIG_DLM_DEBUG=y # # Security options # CONFIG_KEYS=y CONFIG_KEYS_COMPAT=y CONFIG_PERSISTENT_KEYRINGS=y CONFIG_BIG_KEYS=y CONFIG_TRUSTED_KEYS=y CONFIG_ENCRYPTED_KEYS=y # CONFIG_KEY_DH_OPERATIONS is not set # CONFIG_SECURITY_DMESG_RESTRICT is not set CONFIG_SECURITY=y CONFIG_SECURITY_WRITABLE_HOOKS=y CONFIG_SECURITYFS=y CONFIG_SECURITY_NETWORK=y CONFIG_PAGE_TABLE_ISOLATION=y CONFIG_SECURITY_INFINIBAND=y CONFIG_SECURITY_NETWORK_XFRM=y CONFIG_SECURITY_PATH=y CONFIG_INTEL_TXT=y CONFIG_LSM_MMAP_MIN_ADDR=65535 CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y CONFIG_HARDENED_USERCOPY=y CONFIG_HARDENED_USERCOPY_FALLBACK=y # CONFIG_HARDENED_USERCOPY_PAGESPAN is not set # CONFIG_FORTIFY_SOURCE is not set # CONFIG_STATIC_USERMODEHELPER is not set CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 # CONFIG_SECURITY_SMACK is not set # CONFIG_SECURITY_TOMOYO is not set CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_HASH=y CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y # CONFIG_SECURITY_APPARMOR_DEBUG is not set # CONFIG_SECURITY_LOADPIN is not set CONFIG_SECURITY_YAMA=y # CONFIG_SECURITY_SAFESETID is not set CONFIG_INTEGRITY=y CONFIG_INTEGRITY_SIGNATURE=y CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y CONFIG_INTEGRITY_TRUSTED_KEYRING=y # CONFIG_INTEGRITY_PLATFORM_KEYRING is not set CONFIG_INTEGRITY_AUDIT=y CONFIG_IMA=y CONFIG_IMA_MEASURE_PCR_IDX=10 CONFIG_IMA_LSM_RULES=y # CONFIG_IMA_TEMPLATE is not set CONFIG_IMA_NG_TEMPLATE=y # CONFIG_IMA_SIG_TEMPLATE is not set CONFIG_IMA_DEFAULT_TEMPLATE="ima-ng" CONFIG_IMA_DEFAULT_HASH_SHA1=y # CONFIG_IMA_DEFAULT_HASH_SHA256 is not set CONFIG_IMA_DEFAULT_HASH="sha1" # CONFIG_IMA_WRITE_POLICY is not set # CONFIG_IMA_READ_POLICY is not set CONFIG_IMA_APPRAISE=y # CONFIG_IMA_ARCH_POLICY is not set # CONFIG_IMA_APPRAISE_BUILD_POLICY is not set CONFIG_IMA_APPRAISE_BOOTPARAM=y CONFIG_IMA_TRUSTED_KEYRING=y # CONFIG_IMA_BLACKLIST_KEYRING is not set # CONFIG_IMA_LOAD_X509 is not set CONFIG_EVM=y CONFIG_EVM_ATTR_FSUUID=y # CONFIG_EVM_ADD_XATTRS is not set # CONFIG_EVM_LOAD_X509 is not set CONFIG_DEFAULT_SECURITY_SELINUX=y # CONFIG_DEFAULT_SECURITY_APPARMOR is not set # CONFIG_DEFAULT_SECURITY_DAC is not set CONFIG_LSM="yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor" CONFIG_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_ASYNC_PQ=m CONFIG_ASYNC_RAID6_RECOV=m CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_RNG_DEFAULT=y CONFIG_CRYPTO_AKCIPHER2=y CONFIG_CRYPTO_AKCIPHER=y CONFIG_CRYPTO_KPP2=y CONFIG_CRYPTO_KPP=m CONFIG_CRYPTO_ACOMP2=y CONFIG_CRYPTO_RSA=y CONFIG_CRYPTO_DH=m CONFIG_CRYPTO_ECDH=m CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y CONFIG_CRYPTO_GF128MUL=y CONFIG_CRYPTO_NULL=y CONFIG_CRYPTO_NULL2=y CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_SIMD=m CONFIG_CRYPTO_GLUE_HELPER_X86=m CONFIG_CRYPTO_ENGINE=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=y # CONFIG_CRYPTO_CHACHA20POLY1305 is not set # CONFIG_CRYPTO_AEGIS128 is not set # CONFIG_CRYPTO_AEGIS128L is not set # CONFIG_CRYPTO_AEGIS256 is not set # CONFIG_CRYPTO_AEGIS128_AESNI_SSE2 is not set # CONFIG_CRYPTO_AEGIS128L_AESNI_SSE2 is not set # CONFIG_CRYPTO_AEGIS256_AESNI_SSE2 is not set # CONFIG_CRYPTO_MORUS640 is not set # CONFIG_CRYPTO_MORUS640_SSE2 is not set # CONFIG_CRYPTO_MORUS1280 is not set # CONFIG_CRYPTO_MORUS1280_SSE2 is not set # CONFIG_CRYPTO_MORUS1280_AVX2 is not set CONFIG_CRYPTO_SEQIV=y CONFIG_CRYPTO_ECHAINIV=m # # Block modes # CONFIG_CRYPTO_CBC=y # CONFIG_CRYPTO_CFB is not set CONFIG_CRYPTO_CTR=y CONFIG_CRYPTO_CTS=y CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_LRW=m # CONFIG_CRYPTO_OFB is not set CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=y # CONFIG_CRYPTO_KEYWRAP is not set # CONFIG_CRYPTO_NHPOLY1305_SSE2 is not set # CONFIG_CRYPTO_NHPOLY1305_AVX2 is not set # CONFIG_CRYPTO_ADIANTUM is not set # # Hash modes # CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m # # Digest # CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=y # CONFIG_CRYPTO_POLY1305 is not set # CONFIG_CRYPTO_POLY1305_X86_64 is not set CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA1_SSSE3=y CONFIG_CRYPTO_SHA256_SSSE3=y CONFIG_CRYPTO_SHA512_SSSE3=m CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_SHA512=m # CONFIG_CRYPTO_SHA3 is not set # CONFIG_CRYPTO_SM3 is not set # CONFIG_CRYPTO_STREEBOG is not set CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m # # Ciphers # CONFIG_CRYPTO_AES=y # CONFIG_CRYPTO_AES_TI is not set CONFIG_CRYPTO_AES_X86_64=y CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m # CONFIG_CRYPTO_DES3_EDE_X86_64 is not set CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m # CONFIG_CRYPTO_CHACHA20 is not set # CONFIG_CRYPTO_CHACHA20_X86_64 is not set CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m # CONFIG_CRYPTO_SM4 is not set CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_LZO=y # CONFIG_CRYPTO_842 is not set # CONFIG_CRYPTO_LZ4 is not set # CONFIG_CRYPTO_LZ4HC is not set # CONFIG_CRYPTO_ZSTD is not set # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=y CONFIG_CRYPTO_DRBG_HMAC=y CONFIG_CRYPTO_DRBG_HASH=y CONFIG_CRYPTO_DRBG_CTR=y CONFIG_CRYPTO_DRBG=y CONFIG_CRYPTO_JITTERENTROPY=y CONFIG_CRYPTO_USER_API=y CONFIG_CRYPTO_USER_API_HASH=y CONFIG_CRYPTO_USER_API_SKCIPHER=y CONFIG_CRYPTO_USER_API_RNG=m # CONFIG_CRYPTO_USER_API_AEAD is not set # CONFIG_CRYPTO_STATS is not set CONFIG_CRYPTO_HASH_INFO=y CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_PADLOCK=m CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_DEV_PADLOCK_SHA=m CONFIG_CRYPTO_DEV_CCP=y CONFIG_CRYPTO_DEV_CCP_DD=m CONFIG_CRYPTO_DEV_SP_CCP=y CONFIG_CRYPTO_DEV_CCP_CRYPTO=m CONFIG_CRYPTO_DEV_SP_PSP=y CONFIG_CRYPTO_DEV_QAT=m CONFIG_CRYPTO_DEV_QAT_DH895xCC=m CONFIG_CRYPTO_DEV_QAT_C3XXX=m CONFIG_CRYPTO_DEV_QAT_C62X=m CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m CONFIG_CRYPTO_DEV_QAT_C3XXXVF=m CONFIG_CRYPTO_DEV_QAT_C62XVF=m # CONFIG_CRYPTO_DEV_NITROX_CNN55XX is not set CONFIG_CRYPTO_DEV_CHELSIO=m CONFIG_CRYPTO_DEV_VIRTIO=m CONFIG_ASYMMETRIC_KEY_TYPE=y CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y # CONFIG_ASYMMETRIC_TPM_KEY_SUBTYPE is not set CONFIG_X509_CERTIFICATE_PARSER=y # CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set CONFIG_PKCS7_MESSAGE_PARSER=y # CONFIG_PKCS7_TEST_KEY is not set CONFIG_SIGNED_PE_FILE_VERIFICATION=y # # Certificates for signature checking # CONFIG_MODULE_SIG_KEY="certs/signing_key.pem" CONFIG_SYSTEM_TRUSTED_KEYRING=y CONFIG_SYSTEM_TRUSTED_KEYS="" # CONFIG_SYSTEM_EXTRA_CERTIFICATE is not set # CONFIG_SECONDARY_TRUSTED_KEYRING is not set CONFIG_SYSTEM_BLACKLIST_KEYRING=y CONFIG_SYSTEM_BLACKLIST_HASH_LIST="" CONFIG_BINARY_PRINTF=y # # Library routines # CONFIG_RAID6_PQ=m CONFIG_RAID6_PQ_BENCHMARK=y CONFIG_BITREVERSE=y CONFIG_RATIONAL=y CONFIG_GENERIC_STRNCPY_FROM_USER=y CONFIG_GENERIC_STRNLEN_USER=y CONFIG_GENERIC_NET_UTILS=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_PCI_IOMAP=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y CONFIG_ARCH_HAS_FAST_MULTIPLIER=y CONFIG_CRC_CCITT=y CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y # CONFIG_CRC32_SELFTEST is not set CONFIG_CRC32_SLICEBY8=y # CONFIG_CRC32_SLICEBY4 is not set # CONFIG_CRC32_SARWATE is not set # CONFIG_CRC32_BIT is not set # CONFIG_CRC64 is not set # CONFIG_CRC4 is not set # CONFIG_CRC7 is not set CONFIG_LIBCRC32C=m CONFIG_CRC8=m CONFIG_XXHASH=y # CONFIG_RANDOM32_SELFTEST is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_LZ4_DECOMPRESS=y CONFIG_ZSTD_COMPRESS=m CONFIG_ZSTD_DECOMPRESS=m CONFIG_XZ_DEC=y CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y # CONFIG_XZ_DEC_TEST is not set CONFIG_DECOMPRESS_GZIP=y CONFIG_DECOMPRESS_BZIP2=y CONFIG_DECOMPRESS_LZMA=y CONFIG_DECOMPRESS_XZ=y CONFIG_DECOMPRESS_LZO=y CONFIG_DECOMPRESS_LZ4=y CONFIG_GENERIC_ALLOCATOR=y CONFIG_REED_SOLOMON=m CONFIG_REED_SOLOMON_ENC8=y CONFIG_REED_SOLOMON_DEC8=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_BTREE=y CONFIG_INTERVAL_TREE=y CONFIG_XARRAY_MULTI=y CONFIG_ASSOCIATIVE_ARRAY=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT_MAP=y CONFIG_HAS_DMA=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_DMA_DECLARE_COHERENT=y CONFIG_DMA_VIRT_OPS=y CONFIG_SWIOTLB=y CONFIG_DMA_CMA=y # # Default contiguous memory area size: # CONFIG_CMA_SIZE_MBYTES=200 CONFIG_CMA_SIZE_SEL_MBYTES=y # CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set # CONFIG_CMA_SIZE_SEL_MIN is not set # CONFIG_CMA_SIZE_SEL_MAX is not set CONFIG_CMA_ALIGNMENT=8 # CONFIG_DMA_API_DEBUG is not set CONFIG_SGL_ALLOC=y CONFIG_IOMMU_HELPER=y CONFIG_CHECK_SIGNATURE=y CONFIG_CPUMASK_OFFSTACK=y CONFIG_CPU_RMAP=y CONFIG_DQL=y CONFIG_GLOB=y # CONFIG_GLOB_SELFTEST is not set CONFIG_NLATTR=y CONFIG_CLZ_TAB=y CONFIG_CORDIC=m # CONFIG_DDR is not set CONFIG_IRQ_POLL=y CONFIG_MPILIB=y CONFIG_SIGNATURE=y CONFIG_OID_REGISTRY=y CONFIG_UCS2_STRING=y CONFIG_FONT_SUPPORT=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y CONFIG_SG_POOL=y CONFIG_ARCH_HAS_PMEM_API=y CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE=y CONFIG_ARCH_HAS_UACCESS_MCSAFE=y CONFIG_SBITMAP=y CONFIG_PARMAN=m CONFIG_PRIME_NUMBERS=m # CONFIG_STRING_SELFTEST is not set CONFIG_OBJAGG=m # # Kernel hacking # # # printk and dmesg options # CONFIG_PRINTK_TIME=y # CONFIG_PRINTK_CALLER is not set CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7 CONFIG_CONSOLE_LOGLEVEL_QUIET=4 CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4 CONFIG_BOOT_PRINTK_DELAY=y CONFIG_DYNAMIC_DEBUG=y # # Compile-time checks and compiler options # CONFIG_DEBUG_INFO=y CONFIG_DEBUG_INFO_REDUCED=y # CONFIG_DEBUG_INFO_SPLIT is not set # CONFIG_DEBUG_INFO_DWARF4 is not set # CONFIG_GDB_SCRIPTS is not set CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=2048 CONFIG_STRIP_ASM_SYMS=y # CONFIG_READABLE_ASM is not set # CONFIG_UNUSED_SYMBOLS is not set CONFIG_DEBUG_FS=y CONFIG_HEADERS_CHECK=y CONFIG_DEBUG_SECTION_MISMATCH=y CONFIG_SECTION_MISMATCH_WARN_ONLY=y CONFIG_STACK_VALIDATION=y # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1 CONFIG_MAGIC_SYSRQ_SERIAL=y CONFIG_DEBUG_KERNEL=y # # Memory Debugging # # CONFIG_PAGE_EXTENSION is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_PAGE_OWNER is not set # CONFIG_PAGE_POISONING is not set # CONFIG_DEBUG_PAGE_REF is not set CONFIG_DEBUG_RODATA_TEST=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set CONFIG_HAVE_DEBUG_KMEMLEAK=y # CONFIG_DEBUG_KMEMLEAK is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_VM is not set CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y # CONFIG_DEBUG_VIRTUAL is not set CONFIG_DEBUG_MEMORY_INIT=y CONFIG_MEMORY_NOTIFIER_ERROR_INJECT=m # CONFIG_DEBUG_PER_CPU_MAPS is not set CONFIG_HAVE_DEBUG_STACKOVERFLOW=y CONFIG_DEBUG_STACKOVERFLOW=y CONFIG_HAVE_ARCH_KASAN=y CONFIG_CC_HAS_KASAN_GENERIC=y # CONFIG_KASAN is not set CONFIG_KASAN_STACK=1 CONFIG_ARCH_HAS_KCOV=y CONFIG_CC_HAS_SANCOV_TRACE_PC=y # CONFIG_KCOV is not set CONFIG_DEBUG_SHIRQ=y # # Debug Lockups and Hangs # CONFIG_LOCKUP_DETECTOR=y CONFIG_SOFTLOCKUP_DETECTOR=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_HARDLOCKUP_DETECTOR_PERF=y CONFIG_HARDLOCKUP_CHECK_TIMESTAMP=y CONFIG_HARDLOCKUP_DETECTOR=y CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=1 # CONFIG_DETECT_HUNG_TASK is not set # CONFIG_WQ_WATCHDOG is not set CONFIG_PANIC_ON_OOPS=y CONFIG_PANIC_ON_OOPS_VALUE=1 CONFIG_PANIC_TIMEOUT=0 CONFIG_SCHED_DEBUG=y CONFIG_SCHED_INFO=y CONFIG_SCHEDSTATS=y # CONFIG_SCHED_STACK_END_CHECK is not set # CONFIG_DEBUG_TIMEKEEPING is not set # # Lock Debugging (spinlocks, mutexes, etc...) # CONFIG_LOCK_DEBUGGING_SUPPORT=y # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set # CONFIG_DEBUG_RWSEMS is not set # CONFIG_DEBUG_LOCK_ALLOC is not set CONFIG_DEBUG_ATOMIC_SLEEP=y # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set CONFIG_LOCK_TORTURE_TEST=m CONFIG_WW_MUTEX_SELFTEST=m CONFIG_STACKTRACE=y # CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_LIST=y # CONFIG_DEBUG_PI_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set # # RCU Debugging # CONFIG_TORTURE_TEST=m CONFIG_RCU_PERF_TEST=m CONFIG_RCU_TORTURE_TEST=m CONFIG_RCU_CPU_STALL_TIMEOUT=60 # CONFIG_RCU_TRACE is not set # CONFIG_RCU_EQS_DEBUG is not set # CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set CONFIG_NOTIFIER_ERROR_INJECTION=m CONFIG_PM_NOTIFIER_ERROR_INJECT=m # CONFIG_NETDEV_NOTIFIER_ERROR_INJECT is not set CONFIG_FUNCTION_ERROR_INJECTION=y CONFIG_FAULT_INJECTION=y # CONFIG_FAILSLAB is not set # CONFIG_FAIL_PAGE_ALLOC is not set CONFIG_FAIL_MAKE_REQUEST=y # CONFIG_FAIL_IO_TIMEOUT is not set # CONFIG_FAIL_FUTEX is not set CONFIG_FAULT_INJECTION_DEBUG_FS=y # CONFIG_FAIL_FUNCTION is not set # CONFIG_FAIL_MMC_REQUEST is not set # CONFIG_LATENCYTOP is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_HAVE_FENTRY=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_TRACER_MAX_TRACE=y CONFIG_TRACE_CLOCK=y CONFIG_RING_BUFFER=y CONFIG_EVENT_TRACING=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_RING_BUFFER_ALLOW_SWAP=y CONFIG_TRACING=y CONFIG_GENERIC_TRACER=y CONFIG_TRACING_SUPPORT=y CONFIG_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_PREEMPTIRQ_EVENTS is not set # CONFIG_IRQSOFF_TRACER is not set CONFIG_SCHED_TRACER=y CONFIG_HWLAT_TRACER=y CONFIG_FTRACE_SYSCALLS=y CONFIG_TRACER_SNAPSHOT=y # CONFIG_TRACER_SNAPSHOT_PER_CPU_SWAP is not set CONFIG_BRANCH_PROFILE_NONE=y # CONFIG_PROFILE_ANNOTATED_BRANCHES is not set # CONFIG_PROFILE_ALL_BRANCHES is not set CONFIG_STACK_TRACER=y CONFIG_BLK_DEV_IO_TRACE=y CONFIG_KPROBE_EVENTS=y # CONFIG_KPROBE_EVENTS_ON_NOTRACE is not set CONFIG_UPROBE_EVENTS=y CONFIG_BPF_EVENTS=y CONFIG_DYNAMIC_EVENTS=y CONFIG_PROBE_EVENTS=y CONFIG_DYNAMIC_FTRACE=y CONFIG_DYNAMIC_FTRACE_WITH_REGS=y CONFIG_FUNCTION_PROFILER=y # CONFIG_BPF_KPROBE_OVERRIDE is not set CONFIG_FTRACE_MCOUNT_RECORD=y # CONFIG_FTRACE_STARTUP_TEST is not set # CONFIG_MMIOTRACE is not set CONFIG_TRACING_MAP=y CONFIG_HIST_TRIGGERS=y # CONFIG_TRACEPOINT_BENCHMARK is not set CONFIG_RING_BUFFER_BENCHMARK=m # CONFIG_RING_BUFFER_STARTUP_TEST is not set # CONFIG_PREEMPTIRQ_DELAY_TEST is not set # CONFIG_TRACE_EVAL_MAP_FILE is not set CONFIG_TRACING_EVENTS_GPIO=y CONFIG_PROVIDE_OHCI1394_DMA_INIT=y CONFIG_RUNTIME_TESTING_MENU=y # CONFIG_LKDTM is not set # CONFIG_TEST_LIST_SORT is not set # CONFIG_TEST_SORT is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_RBTREE_TEST is not set # CONFIG_INTERVAL_TREE_TEST is not set # CONFIG_PERCPU_TEST is not set CONFIG_ATOMIC64_SELFTEST=y # CONFIG_ASYNC_RAID6_TEST is not set # CONFIG_TEST_HEXDUMP is not set # CONFIG_TEST_STRING_HELPERS is not set # CONFIG_TEST_KSTRTOX is not set CONFIG_TEST_PRINTF=m CONFIG_TEST_BITMAP=m # CONFIG_TEST_BITFIELD is not set # CONFIG_TEST_UUID is not set # CONFIG_TEST_XARRAY is not set # CONFIG_TEST_OVERFLOW is not set # CONFIG_TEST_RHASHTABLE is not set # CONFIG_TEST_HASH is not set # CONFIG_TEST_IDA is not set # CONFIG_TEST_PARMAN is not set CONFIG_TEST_LKM=m # CONFIG_TEST_VMALLOC is not set CONFIG_TEST_USER_COPY=m CONFIG_TEST_BPF=m # CONFIG_FIND_BIT_BENCHMARK is not set CONFIG_TEST_FIRMWARE=m CONFIG_TEST_SYSCTL=m # CONFIG_TEST_UDELAY is not set CONFIG_TEST_STATIC_KEYS=m CONFIG_TEST_KMOD=m # CONFIG_TEST_MEMCAT_P is not set CONFIG_TEST_LIVEPATCH=m # CONFIG_TEST_OBJAGG is not set # CONFIG_TEST_STACKINIT is not set # CONFIG_MEMTEST is not set # CONFIG_BUG_ON_DATA_CORRUPTION is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set CONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y # CONFIG_UBSAN is not set CONFIG_UBSAN_ALIGNMENT=y CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y CONFIG_STRICT_DEVMEM=y # CONFIG_IO_STRICT_DEVMEM is not set CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_EARLY_PRINTK_USB=y CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y CONFIG_EARLY_PRINTK_DBGP=y # CONFIG_EARLY_PRINTK_USB_XDBC is not set # CONFIG_X86_PTDUMP is not set # CONFIG_EFI_PGT_DUMP is not set # CONFIG_DEBUG_WX is not set CONFIG_DOUBLEFAULT=y # CONFIG_DEBUG_TLBFLUSH is not set # CONFIG_IOMMU_DEBUG is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_X86_DECODER_SELFTEST=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 CONFIG_DEBUG_BOOT_PARAMS=y # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # CONFIG_DEBUG_ENTRY is not set # CONFIG_DEBUG_NMI_SELFTEST is not set CONFIG_X86_DEBUG_FPU=y # CONFIG_PUNIT_ATOM_DEBUG is not set CONFIG_UNWINDER_ORC=y # CONFIG_UNWINDER_FRAME_POINTER is not set # CONFIG_UNWINDER_GUESS is not set [-- Attachment #3: job-script.ksh --] [-- Type: text/plain, Size: 7907 bytes --] #!/bin/sh export_top_env() { export suite='aim7' export testcase='aim7' export category='benchmark' export job_origin='/lkp/lkp/.src-20190404-231145/allot/cyclic:p1:linux-devel:devel-hourly/lkp-ivb-ep01/aim7-fs-raid.yaml' export queue_cmdline_keys='branch commit' export queue='validate' export testbox='lkp-ivb-ep01' export tbox_group='lkp-ivb-ep01' export submit_id='5ca81aa20b9a93ec14f3ee02' export job_file='/lkp/jobs/scheduled/lkp-ivb-ep01/aim7-performance-4BRD_12G-xfs-3000-RAID0-disk_rr-debian-x86_64-2-20190406-60436-1x83hp0-3.yaml' export id='4f68864425a5ec9293fde294caa40c7565bd0bb2' export queuer_version='/lkp/lkp/.src-20190406-001603' export arch='x86_64' export commit='fa3fe73bed17967cb623461b166c46dcffb661a7' export need_kconfig='CONFIG_BLK_DEV_RAM=m CONFIG_BLK_DEV=y CONFIG_BLOCK=y CONFIG_MD_RAID0 CONFIG_XFS_FS' export kconfig='x86_64-rhel-7.6' export compiler='gcc-7' export rootfs='debian-x86_64-2018-04-03.cgz' export enqueue_time='2019-04-06 11:18:59 +0800' export _id='5ca81aa30b9a93ec14f3ee03' export _rt='/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7' export user='lkp' export head_commit='417fa9ecbba97f4267e4a83d68864398c30b5d60' export base_commit='79a3aaa7b82e3106be97842dedfd8429248896e6' export branch='linux-devel/devel-hourly-2019040601' export result_root='/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/3' export scheduler_version='/lkp/lkp/.src-20190406-001603' export LKP_SERVER='inn' export max_uptime=3600 export initrd='/osimage/debian/debian-x86_64-2018-04-03.cgz' export bootloader_append='root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/lkp-ivb-ep01/aim7-performance-4BRD_12G-xfs-3000-RAID0-disk_rr-debian-x86_64-2-20190406-60436-1x83hp0-3.yaml ARCH=x86_64 kconfig=x86_64-rhel-7.6 branch=linux-devel/devel-hourly-2019040601 commit=fa3fe73bed17967cb623461b166c46dcffb661a7 BOOT_IMAGE=/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/vmlinuz-5.1.0-rc3-00068-gfa3fe73 max_uptime=3600 RESULT_ROOT=/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/3 LKP_SERVER=inn debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw' export modules_initrd='/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/modules.cgz' export bm_initrd='/osimage/deps/debian-x86_64-2018-04-03.cgz/run-ipconfig_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/lkp_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/rsync-rootfs_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/perf_2019-04-03.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/perf-x86_64-5e7a8ca31926_2019-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/md_2018-06-12.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/fs_2018-06-12.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/aim7-x86_64-_2018-05-18.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/mpstat_2019-03-14.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/turbostat_2018-05-17.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/turbostat-x86_64-d5256b2_2018-05-18.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/mpstat-x86_64-git-1_2019-03-27.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/hw_2016-11-15.cgz' export lkp_initrd='/lkp/lkp/lkp-x86_64.cgz' export site='inn' export LKP_CGI_PORT=80 export LKP_CIFS_PORT=139 export repeat_to=4 export schedule_notify_address= export model='Ivy Bridge-EP' export nr_node=2 export nr_cpu=40 export memory='384G' export hdd_partitions='/dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part1 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part2 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part3 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part4 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part5 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part6 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part7 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part8' export swap_partitions= export rootfs_partition='LABEL=LKP-ROOTFS' export brand='Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz' export kernel='/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/vmlinuz-5.1.0-rc3-00068-gfa3fe73' export dequeue_time='2019-04-06 11:30:55 +0800' export job_initrd='/lkp/jobs/scheduled/lkp-ivb-ep01/aim7-performance-4BRD_12G-xfs-3000-RAID0-disk_rr-debian-x86_64-2-20190406-60436-1x83hp0-3.cgz' [ -n "$LKP_SRC" ] || export LKP_SRC=/lkp/${user:-lkp}/src } run_job() { echo $$ > $TMP/run-job.pid . $LKP_SRC/lib/http.sh . $LKP_SRC/lib/job.sh . $LKP_SRC/lib/env.sh export_top_env run_setup nr_brd=4 ramdisk_size=12884901888 $LKP_SRC/setup/disk run_setup raid_level='raid0' $LKP_SRC/setup/md run_setup fs='xfs' $LKP_SRC/setup/fs run_setup $LKP_SRC/setup/cpufreq_governor 'performance' run_monitor delay=15 $LKP_SRC/monitors/no-stdout/wrapper perf-profile run_monitor $LKP_SRC/monitors/wrapper kmsg run_monitor $LKP_SRC/monitors/no-stdout/wrapper boot-time run_monitor $LKP_SRC/monitors/wrapper iostat run_monitor $LKP_SRC/monitors/wrapper heartbeat run_monitor $LKP_SRC/monitors/wrapper vmstat run_monitor $LKP_SRC/monitors/wrapper numa-numastat run_monitor $LKP_SRC/monitors/wrapper numa-vmstat run_monitor $LKP_SRC/monitors/wrapper numa-meminfo run_monitor $LKP_SRC/monitors/wrapper proc-vmstat run_monitor $LKP_SRC/monitors/wrapper proc-stat run_monitor $LKP_SRC/monitors/wrapper meminfo run_monitor $LKP_SRC/monitors/wrapper slabinfo run_monitor $LKP_SRC/monitors/wrapper interrupts run_monitor $LKP_SRC/monitors/wrapper lock_stat run_monitor $LKP_SRC/monitors/wrapper latency_stats run_monitor $LKP_SRC/monitors/wrapper softirqs run_monitor $LKP_SRC/monitors/one-shot/wrapper bdi_dev_mapping run_monitor $LKP_SRC/monitors/wrapper diskstats run_monitor $LKP_SRC/monitors/wrapper nfsstat run_monitor $LKP_SRC/monitors/wrapper cpuidle run_monitor $LKP_SRC/monitors/wrapper cpufreq-stats run_monitor $LKP_SRC/monitors/wrapper turbostat run_monitor $LKP_SRC/monitors/wrapper sched_debug run_monitor $LKP_SRC/monitors/wrapper perf-stat run_monitor $LKP_SRC/monitors/wrapper mpstat run_monitor $LKP_SRC/monitors/wrapper oom-killer run_monitor $LKP_SRC/monitors/plain/watchdog run_test test='disk_rr' load=3000 $LKP_SRC/tests/wrapper aim7 } extract_stats() { export stats_part_begin= export stats_part_end= $LKP_SRC/stats/wrapper perf-profile $LKP_SRC/stats/wrapper aim7 $LKP_SRC/stats/wrapper kmsg $LKP_SRC/stats/wrapper boot-time $LKP_SRC/stats/wrapper iostat $LKP_SRC/stats/wrapper vmstat $LKP_SRC/stats/wrapper numa-numastat $LKP_SRC/stats/wrapper numa-vmstat $LKP_SRC/stats/wrapper numa-meminfo $LKP_SRC/stats/wrapper proc-vmstat $LKP_SRC/stats/wrapper meminfo $LKP_SRC/stats/wrapper slabinfo $LKP_SRC/stats/wrapper interrupts $LKP_SRC/stats/wrapper lock_stat $LKP_SRC/stats/wrapper latency_stats $LKP_SRC/stats/wrapper softirqs $LKP_SRC/stats/wrapper diskstats $LKP_SRC/stats/wrapper nfsstat $LKP_SRC/stats/wrapper cpuidle $LKP_SRC/stats/wrapper turbostat $LKP_SRC/stats/wrapper sched_debug $LKP_SRC/stats/wrapper perf-stat $LKP_SRC/stats/wrapper mpstat $LKP_SRC/stats/wrapper time aim7.time $LKP_SRC/stats/wrapper dmesg $LKP_SRC/stats/wrapper kmsg $LKP_SRC/stats/wrapper last_state $LKP_SRC/stats/wrapper stderr $LKP_SRC/stats/wrapper time } "$@" [-- Attachment #4: job.yaml --] [-- Type: text/plain, Size: 5455 bytes --] --- #! jobs/aim7-fs-raid.yaml suite: aim7 testcase: aim7 category: benchmark perf-profile: delay: 15 disk: 4BRD_12G md: RAID0 fs: xfs aim7: test: disk_rr load: 3000 job_origin: "/lkp/lkp/.src-20190404-231145/allot/cyclic:p1:linux-devel:devel-hourly/lkp-ivb-ep01/aim7-fs-raid.yaml" #! queue options queue_cmdline_keys: - branch - commit queue: bisect testbox: lkp-ivb-ep01 tbox_group: lkp-ivb-ep01 submit_id: 5ca80cf60b9a932c217d3ff0 job_file: "/lkp/jobs/scheduled/lkp-ivb-ep01/aim7-performance-4BRD_12G-xfs-3000-RAID0-disk_rr-debian-x86_64-201-20190406-11297-wr9us9-0.yaml" id: 83265162a03b5f38b07a869ccbe2e4f2f6a168ee queuer_version: "/lkp/lkp/.src-20190406-001603" arch: x86_64 #! hosts/lkp-ivb-ep01 #! include/category/benchmark kmsg: boot-time: iostat: heartbeat: vmstat: numa-numastat: numa-vmstat: numa-meminfo: proc-vmstat: proc-stat: meminfo: slabinfo: interrupts: lock_stat: latency_stats: softirqs: bdi_dev_mapping: diskstats: nfsstat: cpuidle: cpufreq-stats: turbostat: sched_debug: perf-stat: mpstat: #! include/category/ALL cpufreq_governor: performance #! include/queue/cyclic commit: fa3fe73bed17967cb623461b166c46dcffb661a7 #! include/disk/nr_brd need_kconfig: - CONFIG_BLK_DEV_RAM=m - CONFIG_BLK_DEV=y - CONFIG_BLOCK=y - CONFIG_MD_RAID0 - CONFIG_XFS_FS #! include/md/raid_level #! include/fs/OTHERS #! default params kconfig: x86_64-rhel-7.6 compiler: gcc-7 rootfs: debian-x86_64-2018-04-03.cgz enqueue_time: 2019-04-06 10:20:40.564462025 +08:00 _id: 5ca80cf60b9a932c217d3ff0 _rt: "/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7" #! schedule options user: lkp head_commit: 417fa9ecbba97f4267e4a83d68864398c30b5d60 base_commit: 79a3aaa7b82e3106be97842dedfd8429248896e6 branch: linux-devel/devel-hourly-2019040601 result_root: "/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/0" scheduler_version: "/lkp/lkp/.src-20190406-001603" LKP_SERVER: inn max_uptime: 3600 initrd: "/osimage/debian/debian-x86_64-2018-04-03.cgz" bootloader_append: - root=/dev/ram0 - user=lkp - job=/lkp/jobs/scheduled/lkp-ivb-ep01/aim7-performance-4BRD_12G-xfs-3000-RAID0-disk_rr-debian-x86_64-201-20190406-11297-wr9us9-0.yaml - ARCH=x86_64 - kconfig=x86_64-rhel-7.6 - branch=linux-devel/devel-hourly-2019040601 - commit=fa3fe73bed17967cb623461b166c46dcffb661a7 - BOOT_IMAGE=/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/vmlinuz-5.1.0-rc3-00068-gfa3fe73 - max_uptime=3600 - RESULT_ROOT=/result/aim7/performance-4BRD_12G-xfs-3000-RAID0-disk_rr/lkp-ivb-ep01/debian-x86_64-2018-04-03.cgz/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/0 - LKP_SERVER=inn - debug - apic=debug - sysrq_always_enabled - rcupdate.rcu_cpu_stall_timeout=100 - net.ifnames=0 - printk.devkmsg=on - panic=-1 - softlockup_panic=1 - nmi_watchdog=panic - oops=panic - load_ramdisk=2 - prompt_ramdisk=0 - drbd.minor_count=8 - systemd.log_level=err - ignore_loglevel - console=tty0 - earlyprintk=ttyS0,115200 - console=ttyS0,115200 - vga=normal - rw modules_initrd: "/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/modules.cgz" bm_initrd: "/osimage/deps/debian-x86_64-2018-04-03.cgz/run-ipconfig_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/lkp_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/rsync-rootfs_2018-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/perf_2019-04-03.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/perf-x86_64-5e7a8ca31926_2019-04-03.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/md_2018-06-12.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/fs_2018-06-12.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/aim7-x86_64-_2018-05-18.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/mpstat_2019-03-14.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/turbostat_2018-05-17.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/turbostat-x86_64-d5256b2_2018-05-18.cgz,/osimage/pkg/debian-x86_64-2018-04-03.cgz/mpstat-x86_64-git-1_2019-03-27.cgz,/osimage/deps/debian-x86_64-2018-04-03.cgz/hw_2016-11-15.cgz" lkp_initrd: "/lkp/lkp/lkp-x86_64.cgz" site: inn #! /lkp/lkp/.src-20190406-001603/include/site/inn LKP_CGI_PORT: 80 LKP_CIFS_PORT: 139 oom-killer: watchdog: #! runtime status repeat_to: 2 schedule_notify_address: model: Ivy Bridge-EP nr_node: 2 nr_cpu: 40 memory: 384G hdd_partitions: "/dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part1 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part2 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part3 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part4 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part5 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part6 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part7 /dev/disk/by-id/scsi-36b8ca3a0e650e100228623a40f936347-part8" swap_partitions: rootfs_partition: LABEL=LKP-ROOTFS brand: Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz #! user overrides kernel: "/pkg/linux/x86_64-rhel-7.6/gcc-7/fa3fe73bed17967cb623461b166c46dcffb661a7/vmlinuz-5.1.0-rc3-00068-gfa3fe73" dequeue_time: 2019-04-06 10:23:56.584510126 +08:00 job_state: finished loadavg: 1731.04 792.02 297.52 1/444 7884 start_time: '1554517519' end_time: '1554517636' version: "/lkp/lkp/.src-20190406-001603" [-- Attachment #5: reproduce.ksh --] [-- Type: text/plain, Size: 1041 bytes --] "modprobe" "-r" "brd" "modprobe" "brd" "rd_nr=4" "rd_size=12582912" "mdadm" "-q" "--stop" "/dev/md0" "dmsetup" "remove_all" "wipefs" "-a" "--force" "/dev/ram0" "wipefs" "-a" "--force" "/dev/ram1" "wipefs" "-a" "--force" "/dev/ram2" "wipefs" "-a" "--force" "/dev/ram3" "mdadm" "-q" "--create" "/dev/md0" "--chunk=256" "--level=raid0" "--raid-devices=4" "--force" "--assume-clean" "/dev/ram0" "/dev/ram1" "/dev/ram2" "/dev/ram3" wipefs -a --force /dev/md0 mkfs -t xfs /dev/md0 mkdir -p /fs/md0 mount -t xfs -o inode64 /dev/md0 /fs/md0 for cpu_dir in /sys/devices/system/cpu/cpu[0-9]* do online_file="$cpu_dir"/online [ -f "$online_file" ] && [ "$(cat "$online_file")" -eq 0 ] && continue file="$cpu_dir"/cpufreq/scaling_governor [ -f "$file" ] && echo "performance" > "$file" done echo "500 32000 128 512" > /proc/sys/kernel/sem cat > workfile <<EOF FILESIZE: 1M POOLSIZE: 10M 10 disk_rr EOF echo "/fs/md0" > config ( echo lkp-ivb-ep01 echo disk_rr echo 1 echo 3000 echo 2 echo 3000 echo 1 ) | ./multitask -t ^ permalink raw reply [flat|nested] 41+ messages in thread
end of thread, other threads:[~2022-09-21 11:20 UTC | newest] Thread overview: 41+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-04-04 16:57 [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload Amir Goldstein 2019-04-04 21:17 ` Dave Chinner 2019-04-05 14:02 ` Amir Goldstein 2019-04-07 23:27 ` Dave Chinner 2019-04-08 9:02 ` Amir Goldstein 2019-04-08 14:11 ` Jan Kara 2019-04-08 17:41 ` Amir Goldstein 2019-04-09 8:26 ` Jan Kara 2022-06-17 14:48 ` Amir Goldstein 2022-06-17 15:11 ` Jan Kara 2022-06-18 8:38 ` Amir Goldstein 2022-06-20 9:11 ` Jan Kara 2022-06-21 7:49 ` Amir Goldstein 2022-06-21 8:59 ` Jan Kara 2022-06-21 12:53 ` Amir Goldstein 2022-06-22 3:23 ` Matthew Wilcox 2022-06-22 9:00 ` Amir Goldstein 2022-06-22 9:34 ` Jan Kara 2022-06-22 16:26 ` Amir Goldstein 2022-09-13 14:40 ` Amir Goldstein 2022-09-14 16:01 ` Darrick J. Wong 2022-09-14 16:29 ` Amir Goldstein 2022-09-14 17:39 ` Darrick J. Wong 2022-09-19 23:09 ` Dave Chinner 2022-09-20 2:24 ` Dave Chinner 2022-09-20 3:08 ` Amir Goldstein 2022-09-21 11:20 ` Amir Goldstein 2019-04-08 11:03 ` Jan Kara 2019-04-22 10:55 ` Boaz Harrosh 2019-04-08 10:33 ` Jan Kara 2019-04-08 16:37 ` Davidlohr Bueso 2019-04-08 16:37 ` Davidlohr Bueso 2019-04-11 1:11 ` Dave Chinner 2019-04-16 12:22 ` Dave Chinner 2019-04-18 3:10 ` Dave Chinner 2019-04-18 18:21 ` Davidlohr Bueso 2019-04-18 18:21 ` Davidlohr Bueso 2019-04-20 23:54 ` Dave Chinner 2019-05-03 4:17 ` Dave Chinner 2019-05-03 5:17 ` Dave Chinner 2019-04-08 9:14 ` [xfs] fa3fe73bed: aim7.jobs-per-min -10.9% regression kernel test robot
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.