search for: yonge

HI, Do anyone know where btrfs_print_tree is invoked? thanks. -- Regards, Zhi Yong Wu -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

llvm code generator lowers both integer and pointer types into ixx(say, i16, i32, i64, ...). This make senses for some optimizations. However, integer registers and pointer registers is expilicitly distinguished from each other for some architectures, like TriCore, Blackfin, and our lab prototype dsp, which accelerates address computation and memory access. I have already read this mail thread:

On 2019/10/24 ??11:26, Liu, Yong wrote: > >> -----Original Message----- >> From: Jason Wang [mailto:jasowang at redhat.com] >> Sent: Tuesday, October 22, 2019 9:06 PM >> To: Liu, Yong <yong.liu at intel.com>; mst at redhat.com; Bie, Tiwei >> <tiwei.bie at intel.com> >> Cc: virtualization at lists.linux-foundation.org >> Subject: Re: [PATCH]

David, thanks for your immediate response. Since iPTR is a reserved type for tablegen internal use, can you make a further explanation? On the other hand, it can be simply treated as a register class assignment problem during register allocation. Assume both pointer and integet have a 32 bit width. backend handles it just as to i32. When it performs register allocation, it can retrieve from

Sergei, Thank you for your attention. My target is a custom VLIW DSP. I am not sure dependency dag is correct when it gets scheduled and packetized. Months ago, I submitted a bug at http://llvm.org/bugs/show_bug.cgi?id=17894 which explained more details. I am not sure my understanding of this bug is proper, but modified my local codes this way and it works for my target when scheduling and

We also have this problem, and have added iPTR types to the back end. Our pointers are actually fat pointers, so this also requires tweaking some optimisations (for example, things like to turn GEPs with 64-bit offsets into pointer-sized offsets, but our pointers are larger than any integer type that we support...). Most of the changes are a bit ugly, and I'm loath to upstream them without

Hi Diego, Just to clarify, so did you do an offline upgrade with an existing cluster (3.6.x => 3.10.x)? Thanks. On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I was never able to go from 3.6.x to 3.7.x without downtime. Then > 3.7.x did not work well for me, so I stuck with 3.6.x until recently. > I went from 3.6.x to 3.10.x but downtime was

Hi, all, When I schedule machine instructions in a VLIW way and packetize them, a problem is encountered, and I will show it use a simplified case as follows. ############ original instruction sequence ... insn1 ... jump LBB0_xx ... LBB0_xx: ... ############ expected instruction sequence after scheduling and packetizing insn1; jump LBB0_xx ... LBB0_xx: ... ############ generated instruction

Hi, In our version of LLVM, we've added different-sized iPTR* types, so we have an iPTR256 for our fat pointers. This causes some problems with constraints, because the way that TableGen resolves constraints is not expected to handle multiple pointer types. We've added a flag that can be set on a per-backend basis to turn this off. Our problem is perhaps a bit different form yours,

Yes, I did an offline upgrade. 1. Stop all clients using gluster servers. 2. Stop glusterfsd and glusterd on both servers. 3. Backed up /var/lib/gluster* in all servers just to be safe. 4. Upgraded all servers from 3.6.x to 3.10.x (I did not have quotas or anything that required special steps) 5. Started gluster daemons again and confirmed everything was fine prior to letting clients connect. 5.

On Fri, Oct 10, 2014 at 04:03:26PM +0800, Zhi Yong Wu wrote: > On Fri, Oct 10, 2014 at 3:39 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote: > >> HI, Richard > >> > >> Is there any plan to make daemon to directly run on the hypervisor, > >> not starting a guest? e.g. directly export

On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> Yeah, but why did it happen when i directly issue guest VM via above command? > > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket > first [on RHEL 5 -- it works differently upstream]. Without the > socket

On Sun, Jun 23, 2013 at 04:57:44PM +0100, David Chisnall wrote: > Hi, > > In our version of LLVM, we've added different-sized iPTR* types, so we have an iPTR256 for our fat pointers. This causes some problems with constraints, because the way that TableGen resolves constraints is not expected to handle multiple pointer types. We've added a flag that can be set on a per-backend

Dear all: a quick question: I am used to apply rm(list=()) regularly to remove all old codes in preventing them creeping in current analysis.however, with that application, functions I wrote are also removed. please let me know how to keep the thing you want while remove those you don't. thank you best yong

On Mon, Sep 29, 2014 at 1:14 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 12:55:04AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> >> Yeah, but why did it happen when i directly issue guest VM

On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 01:22:19AM +0800, Zhi Yong Wu wrote: >> Yes, I am trying to run it in Xen Domain0. I thought that we can use >> Domain0 as a public libguestfs VM, This will avoid starting a new >> guest for virt-xxx every time, But Domain0 has no corresponding qemu >> task. So

From: Nicholas Bellinger <nab at linux-iscsi.org> This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID instance) when connected to individual tcm_vhost endpoints as requested by Paolo. This ensures that virtio-scsi LLD only attempts to scan target IDs up to VIRTIO_SCSI_MAX_TARGET when

From: Nicholas Bellinger <nab at linux-iscsi.org> This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID instance) when connected to individual tcm_vhost endpoints as requested by Paolo. This ensures that virtio-scsi LLD only attempts to scan target IDs up to VIRTIO_SCSI_MAX_TARGET when

On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote: > HI, Richard > > Is there any plan to make daemon to directly run on the hypervisor, > not starting a guest? e.g. directly export a guest image to be a block > device on the hypervisor? Not in 1.28, but adding lxc:// support to the libvirt backend (src/launch-libvirt.c) would be fairly easy. It's an idea that has

Hello, we wounder whether is it possible to add OSTs to the Lustre with quota support without making it offline? We tried to do this but all quota information was lost. Despite the fact that OST was formatted with quota support we are receiving this error message: Lustre: 3743:0:(lproc_quota.c:447:lprocfs_quota_wr_type()) lustrefs-OST0016: quotaon failed because quota files