Displaying 11 results from an estimated 11 matches similar to: "Aggregate on identical link attributes"
2015 Feb 18
2
[LLVMdev] local variable in Pattern definition?
Hi guys,
When I am trying to define pattern in a multi class, I got something like this:
“
multi class P_PAT<string sty, SDNode tNode>
{
def : Pat<( !cast<ValueType>(“v2” # sty) (tNode !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” # sty):$src2) ),
( add !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” #
2007 Mar 16
2
re: o2hb_do_disk_heartbeat:963 ERROR: Device "sdb1" another node is heartbeating in our slot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Folks,
I'm trying to wrap my head around something that happened in our environment.
Basically, we noticed the error in /var/log/messages with no other errors.
"Mar 16 13:38:02 dbo3 kernel: (3712,3):o2hb_do_disk_heartbeat:963 ERROR: Device "sdb1": another node is
heartbeating in our slot!"
Usually there are a
2019 Nov 12
0
[PATCH v3 06/14] RDMA/hfi1: Use mmu_interval_notifier_insert for user_exp_rcv
From: Jason Gunthorpe <jgg at mellanox.com>
This converts one of the two users of mmu_notifiers to use the new API.
The conversion is fairly straightforward, however the existing use of
notifiers here seems to be racey.
Tested-by: Dennis Dalessandro <dennis.dalessandro at intel.com>
Signed-off-by: Jason Gunthorpe <jgg at mellanox.com>
---
drivers/infiniband/hw/hfi1/file_ops.c
2019 Oct 28
1
[PATCH v2 06/15] RDMA/hfi1: Use mmu_range_notifier_inset for user_exp_rcv
From: Jason Gunthorpe <jgg at mellanox.com>
This converts one of the two users of mmu_notifiers to use the new API.
The conversion is fairly straightforward, however the existing use of
notifiers here seems to be racey.
Cc: Mike Marciniszyn <mike.marciniszyn at intel.com>
Cc: Dennis Dalessandro <dennis.dalessandro at intel.com>
Signed-off-by: Jason Gunthorpe <jgg at
2010 Mar 15
1
[LLVMdev] CFG as DOT: where do node addresses come from?
Hi,
The -dot-cfg option of opt will write a diagram of an analyzed
function's CFG to DOT format. If you then open the DOT file, you will
see that the BasicBlocks are uniquely identified with hexadecimal
addresses. For example, an edge from one block to another may look like:
Node0x10026b0:s0 -> Node0x1004c20;
I've been trying to figure out where these hexadecimal addresses
2009 Jan 10
5
[Bug 19491] New: S-video & composite output
http://bugs.freedesktop.org/show_bug.cgi?id=19491
Summary: S-video & composite output
Product: xorg
Version: 7.4
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
ReportedBy: monnier at
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others
2012 Jul 27
1
kernel BUG at fs/buffer.c:2886! Linux 3.5.0
Hello
Get this on first write made ( by deliver sending mail to inform of the
restart of services )
Home partition (the one receiving the mail) is based on ocfs2 created
from drbd block device in primary/primary mode
These drbd devices are based on lvm.
system is running linux-3.5.0, identical symptom with linux 3.3 and 3.2
but working with linux 3.0 kernel
reproduced on two machines ( so
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others
2008 Aug 21
0
kickstart error on 5.2 exception
Hi,
I am trying to get my kickstart file that worked under 5.1 to work under 5.2 centos x86_64.
This is the error that I get.
On the screen it says Exception occured and gives me the option to save it. This is that file.
I dont see any odd that would cause it to crash.
Can anyone help. My kickstart file is in the mix below.
Seems to be related to network, my line seems fine (I think) for
2006 Jul 26
5
linux-2.6-xen.hg
Hi,
Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being
updated? if not, what''s the preferred Linux tree to track that has all
of the Xen bits?
Thanks,
Muli
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel