16c00db4bb
Pull AFS fixes from David Howells:
"Here's a set of patches that fix a number of bugs in the in-kernel AFS
client, including:
- Fix directory locking to not use individual page locks for
directory reading/scanning but rather to use a semaphore on the
afs_vnode struct as the directory contents must be read in a single
blob and data from different reads must not be mixed as the entire
contents may be shuffled about between reads.
- Fix address list parsing to handle port specifiers correctly.
- Only give up callback records on a server if we actually talked to
that server (we might not be able to access a server).
- Fix some callback handling bugs, including refcounting,
whole-volume callbacks and when callbacks actually get broken in
response to a CB.CallBack op.
- Fix some server/address rotation bugs, including giving up if we
can't probe a server; giving up if a server says it doesn't have a
volume, but there are more servers to try.
- Fix the decoding of fetched statuses to be OpenAFS compatible.
- Fix the handling of server lookups in Cache Manager ops (such as
CB.InitCallBackState3) to use a UUID if possible and to handle no
server being found.
- Fix a bug in server lookup where not all addresses are compared.
- Fix the non-encryption of calls that prevents some servers from
being accessed (this also requires an AF_RXRPC patch that has
already gone in through the net tree).
There's also a patch that adds tracepoints to log Cache Manager ops
that don't find a matching server, either by UUID or by address"
* tag 'afs-fixes-20180514' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs:
afs: Fix the non-encryption of calls
afs: Fix CB.CallBack handling
afs: Fix whole-volume callback handling
afs: Fix afs_find_server search loop
afs: Fix the handling of an unfound server in CM operations
afs: Add a tracepoint to record callbacks from unlisted servers
afs: Fix the handling of CB.InitCallBackState3 to find the server by UUID
afs: Fix VNOVOL handling in address rotation
afs: Fix AFSFetchStatus decoder to provide OpenAFS compatibility
afs: Fix server rotation's handling of fileserver probe failure
afs: Fix refcounting in callback registration
afs: Fix giving up callbacks on server destruction
afs: Fix address list parsing
afs: Fix directory page locking
47 lines
No EOL
2.9 KiB
JSON
47 lines
No EOL
2.9 KiB
JSON
[
|
|
{
|
|
"PublicDescription": "This event counts all instruction fetches, not including most uncacheable\r\nfetches.",
|
|
"EventCode": "0x80",
|
|
"Counter": "0,1",
|
|
"UMask": "0x3",
|
|
"EventName": "ICACHE.ACCESSES",
|
|
"SampleAfterValue": "200003",
|
|
"BriefDescription": "Instruction fetches"
|
|
},
|
|
{
|
|
"PublicDescription": "This event counts all instruction fetches from the instruction cache.",
|
|
"EventCode": "0x80",
|
|
"Counter": "0,1",
|
|
"UMask": "0x1",
|
|
"EventName": "ICACHE.HIT",
|
|
"SampleAfterValue": "200003",
|
|
"BriefDescription": "Instruction fetches from Icache"
|
|
},
|
|
{
|
|
"PublicDescription": "This event counts all instruction fetches that miss the Instruction cache or produce memory requests. This includes uncacheable fetches. An instruction fetch miss is counted only once and not once for every cycle it is outstanding.",
|
|
"EventCode": "0x80",
|
|
"Counter": "0,1",
|
|
"UMask": "0x2",
|
|
"EventName": "ICACHE.MISSES",
|
|
"SampleAfterValue": "200003",
|
|
"BriefDescription": "Icache miss"
|
|
},
|
|
{
|
|
"PublicDescription": "Counts the number of times the MSROM starts a flow of UOPS. It does not count every time a UOP is read from the microcode ROM. The most common case that this counts is when a micro-coded instruction is encountered by the front end of the machine. Other cases include when an instruction encounters a fault, trap, or microcode assist of any sort. The event will count MSROM startups for UOPS that are speculative, and subsequently cleared by branch mispredict or machine clear. Background: UOPS are produced by two mechanisms. Either they are generated by hardware that decodes instructions into UOPS, or they are delivered by a ROM (called the MSROM) that holds UOPS associated with a specific instruction. MSROM UOPS might also be delivered in response to some condition such as a fault or other exceptional condition. This event is an excellent mechanism for detecting instructions that require the use of MSROM instructions.",
|
|
"EventCode": "0xE7",
|
|
"Counter": "0,1",
|
|
"UMask": "0x1",
|
|
"EventName": "MS_DECODED.MS_ENTRY",
|
|
"SampleAfterValue": "200003",
|
|
"BriefDescription": "Counts the number of times entered into a ucode flow in the FEC. Includes inserted flows due to front-end detected faults or assists. Speculative count."
|
|
},
|
|
{
|
|
"PublicDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction.",
|
|
"EventCode": "0xE9",
|
|
"Counter": "0,1",
|
|
"UMask": "0x1",
|
|
"EventName": "DECODE_RESTRICTION.PREDECODE_WRONG",
|
|
"SampleAfterValue": "200003",
|
|
"BriefDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction"
|
|
}
|
|
] |