search for: remapping

http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html Stepping B-3 has two errata (#47 and #53) related to Interrupt remapping, to which the workaround is for the BIOS to completely disable interrupt remapping. These errata are fixed in stepping C-2. Unfortunately this chipset is very common and many BIOSes are not disabling remapping. We can detect this in Xen and prevent turning on remapping in the first place. Howev...

Hi, Just started using an asterisk-based PBX with Polycom IP501 phones. Am Fairly satisfied and am starting to get into FTP setup of the phones. Have figured out most things except for how button remapping works. In sip.cfg, I have this entry: <keys key.IP_500.31.function.prim="DoNotDisturb"></keys> This works as expected but if I try to change the remapping to any other value like "MyStatus", "SpeedDialMenu", or "BuddyStatus", it doesn't...

For IOAPIC interrupt remapping, it only needs to remap ioapci RTE, should not remap other IOAPIC registers, which are IOAPIC ID, VERSION and Arbitration ID. This patch adds the check for this and only remap ioapci RTE. Signed-off-by: Anthony Xu <anthony.xu@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com&gt...

I want to run the same application installed in 2 Wine bottles (using Wibom) at the same time. Only one can run, not both. Because the app needs to access port numbers 10205,10206, etc., I suspect that running 2 of it (even from separate bottles) causes conflicts at the ports. I wonder if there is a way to remap the port numbers through Wine to different Linux port numbers?

...\\ / In /etc/inetd.conf the -m parameter is added: Tftp ... /usr/libexec/tftpd tftpd -m /etc/tftpd.remap -s /tftpboot Result: The TFTP-daemon dosen't start. I've checked the man pages and there is no -m paramter (like on Linux). Does the build-in TFTP-Dameon in OpenBSD has no feature for remapping? If yes, how do I have to enable it? If no, how can I install the TFTPD-HPA 0.49 on OpenBSD 4.4? Regards Hans

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Sig...

Hi, Found CloneBasicBlock utility only does the cloning without any remapping. Consider below example: Input block: sw.epilog: ; preds = %sw.bb20, %sw.bb15, %sw.bb10, %sw.bb6, %sw.bb2, %sw.bb, %while.body, %if.end29 %no_final.1 = phi i32 [ %no_final.055, %while.body ], [ 1, %if.end29 ], [ %no_final.055, %sw.bb20 ], [ %no_final.055,...

I have an Intel e1000e NIC which I put into passthrough for an HVM domain under Xen 4.2. All the corresponding hardware protections are enabled on my system (DMA + Interrupt remapping), however, once in a while I get a SERR NMI in dom0 (NMI - PCI sys error (SERR) in xl dmesg). I am wondering about its exact reason. I am thinking in the following way: [+] Under Intel VT-x, interrupts are virtualized, thus all the interrupts coming from my HVM domain should be handled by the corr...

...map: input: startup-config Jan 13 21:47:50 proxy in.tftpd[25438]: remap: done Jan 13 21:47:50 proxy in.tftpd[25438]: RRQ from 192.168.0.12 filename startup-config I think that I don't have the remap_file sytax correct. the following it what I have in there currently. # This file defines name remapping for incoming router configs # It will rename the startup-config to the ip address of the Router # sending the config to the tftpd server r startup-config/startup The documentation also mentions being able to use specific replacement patterns. such as using the ip address of the device that is send...

Hello, This about remapping in the HPA tftp server. A client does request for '/tftpboot/ncd4/foo' which should be 'ncd4/foo' I have created a remap file that looks now like this: r tftpboot/ncd4/modshmx/login.hmx ncd4/modshmx/login.hmx r tftpboot/ncd4/modshmx/setup.hmx ncd4/modshmx/setup.hmx r tftpboot/nc...

...a/tftpd/tftpd.8.in +++ b/tftpd/tftpd.8.in @@ -155,7 +155,7 @@ or .B utimeout option is negotiated. The default is 1000000 (1 second.) .TP -\fB\-\-mapfile\fP \fIremap-file\fP, \fB\-m\fP \fIremap-file\fP +\fB\-\-map-file\fP \fIremap-file\fP, \fB\-m\fP \fIremap-file\fP Specify the use of filename remapping. The .I remap-file is a file containing the remapping rules. See the section on filename @@ -238,7 +238,7 @@ option, but crash with an error if they actually get the option accepted by the server. .SH "FILENAME REMAPPING" The -.B \-\-mapfile +.B \-\-map-file option specifies a fil...

Hi - Has anybody been able to successfully remap SpeedDials on Polycom phones? The manual seems to indicate that you can, and I followed the advice in this list message: http://lists.digium.com/pipermail/asterisk-users/2005-October/129142.html The result I get is that the remapped buttons act as the VolumeUp button, rather than as a speed dial. My configs look like this: <Mac

[1.2]-S.T.A.L.K.E.R.:SoC - Remapping keys? Hi, I am running Wine 1.2 on Ubuntu 10.04 32bit Linux. I wish to remap the movement keys in: S.T.A.L.K.E.R.: Shadow of Chernobyl, but when I try, it always maps "Pause" ? Any help would be appreciated! Running game through Valve's Steam client. Game seems to work fine otherw...

...36 version 3 interrupt remap entries shared and old ones not cleared on AMD IOMMUs UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= To avoid an erratum in early hardware, the Xen AMD IOMMU code by default chooses to use a single interrupt remapping table for the whole system. This sharing implies that any guest with a passed through PCI device that is bus mastering capable can inject interrupts into other guests, including domain 0. Furthermore, regardless of whether a shared interrupt remapping table is in use, old entries are not always c...

...ik) PPC and x86, and x86 does not yet promise any kind >>> >> of stability. >> > >> > Hmm I think Jan (cc) said it was already used out there. > Yes, no known issues with vt-d emulation for almost a year now. Error > reporting could be improved, and interrupt remapping is still missing, > but those are minor issues in this context. On the other hand interrupt remapping is absolutely necessary for production use, hence my point that x86 does not promise API stability. ("Any kind of stability" actually didn't include crashes; those are not expect...

...ik) PPC and x86, and x86 does not yet promise any kind >>> >> of stability. >> > >> > Hmm I think Jan (cc) said it was already used out there. > Yes, no known issues with vt-d emulation for almost a year now. Error > reporting could be improved, and interrupt remapping is still missing, > but those are minor issues in this context. On the other hand interrupt remapping is absolutely necessary for production use, hence my point that x86 does not promise API stability. ("Any kind of stability" actually didn't include crashes; those are not expect...

Hi, Without this patch, I get a "remap rules cannot be inverted" error message with any remap rule: --- tftp-hpa-0.40/tftpd/remap.c.old 2005-03-16 16:34:34.000000000 -0500 +++ tftp-hpa-0.40/tftpd/remap.c 2005-03-16 16:22:49.000000000 -0500 @@ -275,6 +275,7 @@ int lineno = 0; int err = 0; + memset(this_rule, '\0', sizeof(struct rule)); while ( lineno++, fgets(line,

During the conversion process, hd* block devices under Xen are mapped to sd* devices for use under guestfs. These sd devices are later remapped to vd* (or sd/hd) devices, for future use under kvm. The current code fails to track the original hd* device names. This causes subsequent remappings of the block devices (in such places as /etc/fstab, and /boot/grub/menu.lst), to skip the hd* devices, which leads to a later failure of the guest. This patch adds a hash to track the hd->sd remap, and later uses that hash to add hd->vd maps to the table. Mike Latimer (1): Track hd sd bl...

On 28/07/2015 18:42, Jan Kiszka wrote: > > On the other hand interrupt remapping is absolutely necessary for > > production use, hence my point that x86 does not promise API stability. > > Well, we currently implement the features that the Q35 used to expose. > Adding interrupt remapping will require a new chipset and/or a hack > switch to ignore compatibilit...

On 28/07/2015 18:42, Jan Kiszka wrote: > > On the other hand interrupt remapping is absolutely necessary for > > production use, hence my point that x86 does not promise API stability. > > Well, we currently implement the features that the Q35 used to expose. > Adding interrupt remapping will require a new chipset and/or a hack > switch to ignore compatibilit...