search for: 0b00

...t8), (ins pcoffset8:$offset), !strconcat("lda", "\t", "${offset}", ",", "pc"), 0x00, 0xA6, [] > { let Inst{23-16} = offset{7-0}; let Inst{15} = 0b1; let Inst{14-13} = 0b00; let Inst{12-8} = 0b01100; let Inst{7-0} = opcode; } def LDAi16oPC : MC6809LoadIndexed_i16oPC_P1< (outs GR8:$dst8), (ins pcoffset16:$offset), !strconcat("lda", "\t", "${offset}", ",", "pc"),...

...> > > It has 4 possible values: > > > values 0x1, 0x11 are written by driver values 0x0, 0x10 are written > > > by device > > > > The 0x prefix might add to the confusion here. It is really just two > > bits, no? > > Ouch. Yes I meant 0b. Thanks! 0b00, 0b10 are written by device? I suppose device can only clear high bit, can keep low bit no change. Then the value written by device can be either 0b01 or 0b00, but 0b10 means to set high bit, no? > > > > each time driver writes out a descriptor, it must make sure that the > > &g...

...> > > It has 4 possible values: > > > values 0x1, 0x11 are written by driver values 0x0, 0x10 are written > > > by device > > > > The 0x prefix might add to the confusion here. It is really just two > > bits, no? > > Ouch. Yes I meant 0b. Thanks! 0b00, 0b10 are written by device? I suppose device can only clear high bit, can keep low bit no change. Then the value written by device can be either 0b01 or 0b00, but 0b10 means to set high bit, no? > > > > each time driver writes out a descriptor, it must make sure that the > > &g...

...e, 0b01), (ins SpecialReg:$dst, Src0RC:$a), (ins Src0RC:$a)); ... } multiclass MultSrc1Spec<bits<5> subOpcode, bits<2> op0t, string opcodeStr, RegisterClass RegType> { def _allspecial: MultSrcOneDestInst<subOpcode, op0t, 0b00, IO_MultSrc<op0t, SpecialReg>.outsDefault, IO_MultSrc<op0t, SpecialReg>.insDefault>; ... } multiclass TwoSrcOneDestSpec<bits<5> subOpcode, string opcodeStr> { defm _dds: MultSrc1Spec<subOpcode, 0b10, opcodeStr, S...

...ions of target RegisterClass (outs) are different in t2LDRSB and t2LDRSB_PRE. While t2LDRSB uses rGPR, t2LDRSB_PRE uses GPR. I wonder if lr and pc are already prevented from being allocated in pre-indexing case, because of some register hint that is being enforced? defm t2LDRSB : T2I_ld<1, 0b00, "ldrsb", IIC_iLoad_bh_i, IIC_iLoad_bh_si, rGPR, UnOpFrag<(sextloadi8 node:$Src)>>; def t2LDRSB_PRE : T2Ipreldst<1, 0b00, 1, 1, (outs GPR:$Rt, GPR:$Rn_wb), (ins t2addrmode_imm8:$addr), AddrModeT...

> > On 9/25/2017 6:03 PM, Shane Ryoo via llvm-dev wrote: > > MultSrcOneDestInst<subOpcode, op0t, 0b00, > > IO_MultSrc<op0t, SpecialReg>.outsDefault, > > IO_MultSrc<op0t, SpecialReg>.insDefault>; > I suspect that the use of IO_MultSrc here is the culprit. TableGen has > some limitations here, when it comes to instan...

..., qemu-system-x86_64 substituted for qemu-kvm, and the path changed from your arguments I get: 9pnet_virtio: no channels available VFS: Cannot open root device "root" or unknown-block(0,0): error -2 Please append a correct "root=" boot option; here are the available partitions: 0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014 Thanks, Christopher -- Employee of Qualcomm Innovatio...

...e >> path changed from your arguments I get: >> >> 9pnet_virtio: no channels available >> VFS: Cannot open root device "root" or unknown-block(0,0): error -2 >> Please append a correct "root=" boot option; here are the available partitions: >> 0b00 1048575 sr0 driver: sr >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) >> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS >> rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014 > > I'm pretty sur...

Hey all, Just downloaded the new Xen 4.0 and ran Make xen Make tools Make stubdom Copied the new files from dist/install Im already running pv_ops 2.6.31.6 kernel. When I boot i get (XEN) Panic on CPU 0: (XEN) IO-APIC + timer doesn''t work! I have tried booting with noapic boot option but makes no difference. The system worked fine on 3.4.2 CPU is AMD.

On Sun, Oct 01, 2017 at 04:08:29AM +0000, Michael S. Tsirkin wrote: >On Thu, Sep 28, 2017 at 09:44:35AM +0000, Liang, Cunming wrote: >> >> Get it now. Please correct me if I missing something. >> >> >> Flags status hints, >> >> - DESC_DRIVER only: driver owns the descriptor w/o available info ready for device to use >> >> - DESC_DRIVER |

On Sun, Oct 01, 2017 at 04:08:29AM +0000, Michael S. Tsirkin wrote: >On Thu, Sep 28, 2017 at 09:44:35AM +0000, Liang, Cunming wrote: >> >> Get it now. Please correct me if I missing something. >> >> >> Flags status hints, >> >> - DESC_DRIVER only: driver owns the descriptor w/o available info ready for device to use >> >> - DESC_DRIVER |

Hi all, a newbie question. I''m trying to install lenny guest image (in an img file) on my lenny Dom0 by following the http://wiki.debian.org/Xen: xm create -c xm-debian.cfg install=true install-mirror=ftp://ftp.XX.debian.org/debian i created the xen-lenny-image.img using dd, format is ext3. disk is defined as (cfg file): disk =

I was playing around with btrfs, and did a mkfs.btrfs on one of my partition. Mistakes, it was my data partition (ext3 based). I have not yet mounted the device, but the mkfs.btrfs continued to completion. Is it possible to salvage my ext3 filesystem? Anyway to reverse the effect of mkfs.btrfs? Thank you for your help/answer. -- Regards, Peter Teoh

...n 172.16.1.40 : hping -t 1 --syn -p 666 172.16.1.40 This is the icmp packet we'll get from 172.16.1.40 : 17:07:46.709230 172.16.1.40 > 172.16.1.28: icmp: time exceeded in-transit 0x0000 45c0 0044 eaa6 0000 ff01 75f1 ac10 0128 E..D......u....( 0x0010 ac10 0118 0b00 516d 0000 0000 4500 0028 ......Qm....E..( 0x0020 b0f3 0000 0106 ac8a ac10 0118 ac10 031a <-+ ................ 0x0030 04bd 0016 3206 3ec0 0490 00b4 5002 0200 | ....2.>.....P... 0x0040 d6b2 00^0 | ......

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the

I booted a Gentoo Linux installation in QEMU with a 9P rootfs as follows: sudo qemu-kvm -cpu host -m 1024 -kernel /mnt/test/usr/src/linux-3.13-rc1/arch/x86/boot/bzImage -append 'root=/dev/root rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' -serial stdio -fsdev local,id=root,path=/mnt/test,security_model=none -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root

I booted a Gentoo Linux installation in QEMU with a 9P rootfs as follows: sudo qemu-kvm -cpu host -m 1024 -kernel /mnt/test/usr/src/linux-3.13-rc1/arch/x86/boot/bzImage -append 'root=/dev/root rootfstype=9p rootflags=trans=virtio,version=9p2000.L ro console=ttyS0' -serial stdio -fsdev local,id=root,path=/mnt/test,security_model=none -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root

.... 0ac0: ff 01 4c 4e 4b 44 00 12 0c 04 0b ff ff 0a 02 4c ..LNKD.........L 0ad0: 4e 4b 41 00 12 0c 04 0b ff ff 0a 03 4c 4e 4b 42 NKA.........LNKB 0ae0: 00 08 41 52 30 36 12 2c 04 12 09 04 0b ff ff 00 ..AR06.,........ 0af0: 00 0a 12 12 09 04 0b ff ff 01 00 0a 13 12 0a 04 ................ 0b00: 0b ff ff 0a 02 00 0a 10 12 0a 04 0b ff ff 0a 03 ................ 0b10: 00 0a 11 08 50 52 30 37 12 34 04 12 0b 04 0b ff ....PR07.4...... 0b20: ff 00 4c 4e 4b 44 00 12 0b 04 0b ff ff 01 4c 4e ..LNKD........LN 0b30: 4b 41 00 12 0c 04 0b ff ff 0a 02 4c 4e 4b 42 00 KA.........LNKB. 0b40: 12...