search for: turd

...ed. I nuked my build directory. Ran >> configure --enable-optimized. Ran make. Same problem. > > What does your <build>/lib/Target/X86/X86GenInstrNames.inc file look like? Are the LOCK_OR* bits in there? User error! I had previously run CMake in the source directory, and it left turd files scattered everywhere (including a turd X86GenInstrNames.inc alongside X86.h). For some reason, 'svn status' is lying to me about what's under version control and what isn't, so I have to nuke the whole thing and start over. :-/ Sorry for the noise. -- Eric Niebler BoostPro...

...the IOMMU and non-IOMMU path are completely equivalent. We can provide that guarantee for our secure VM case, but not generally so if we were to go down the route of a quirk in virtio, it might be better to make it painfully obvious that it's specific to that one case with a different kind of turd: - if (xen_domain()) + if (xen_domain() || pseries_secure_vm()) return true; So to summarize, and make sure I'm not missing something, the two approaches at hand are either: 1- The above, which is a one liner and contained in the guest, so that's nice, but also means another turd in v...

...the IOMMU and non-IOMMU path are completely equivalent. We can provide that guarantee for our secure VM case, but not generally so if we were to go down the route of a quirk in virtio, it might be better to make it painfully obvious that it's specific to that one case with a different kind of turd: - if (xen_domain()) + if (xen_domain() || pseries_secure_vm()) return true; So to summarize, and make sure I'm not missing something, the two approaches at hand are either: 1- The above, which is a one liner and contained in the guest, so that's nice, but also means another turd in v...

...path are completely equivalent. > > We can provide that guarantee for our secure VM case, but not generally so if > we were to go down the route of a quirk in virtio, it might be better to > make it painfully obvious that it's specific to that one case with a different > kind of turd: > > - if (xen_domain()) > + if (xen_domain() || pseries_secure_vm()) > return true; I don't think it's pseries specific actually. E.g. I suspect AMD SEV might benefit from the same kind of hack. > So to summarize, and make sure I'm not missing something, the two ap...

...alent. > > > > We can provide that guarantee for our secure VM case, but not generally so if > > we were to go down the route of a quirk in virtio, it might be better to > > make it painfully obvious that it's specific to that one case with a different > > kind of turd: > > > > - if (xen_domain()) > > + if (xen_domain() || pseries_secure_vm()) > > return true; > > I don't think it's pseries specific actually. E.g. I suspect AMD SEV > might benefit from the same kind of hack. As long as they can provide the same guaran...

Hi, there: I wanna use plug-in "file_column" to upload image to the server. In my test app, the view is as follow & it works well: ==================== <h1>New entry</h1> <%= error_messages_for ''entry'' %> <% form_tag ''create'', :multipart => true do -%> <p><label

...n that I could use for storing password files? Ideally, we'd avoid one large file to prevent locking issues and would also keep the passwd-file setup since it's simple. It would be possible to have the password files in a separate dir, but over time I'm guessing that would lead to nfs turds? Easy to clean up I suppose, but maybe there's a simpler solution I'm missing? George

On May 17, 2011, at 2:50 AM, Eric Niebler wrote: > On 5/17/2011 2:58 AM, Eric Christopher wrote: >> On May 14, 2011, at 3:08 AM, Eric Niebler wrote: >> >>> Just a heads up that the llvm build appears to be broken on cygwin. I >>> haven't investigated, but here's the failures: >>> >>> llvm[3]: Compiling X86ISelDAGToDAG.cpp for

Our asterisk server has been up and running for over a year and it works great. I have emails going to my account as an attachment and I can listen to them on the desktop and it works fine. I just got a T-Mobile MDA that runs Windows Pocket (or whatever they call it) and it can check email. If I have it download the email, it gets the attachment, but it can't seem to play it (it CAN

...true - the cost isn't zero. Of the top of my head... #1 The project will mix and blend with other programming models - The shared runtime should cover all the popular stuff and "this" #2 User confusion - Promoting this over other more established projects and models is just another turd in the pot Lots of things are interesting.. lets take Legion as an example.. that little heard of project at *least* has a bunch of examples and more docs than SE.. https://github.com/StanfordLegion/legion/tree/stable/examples Why do I feel so strongly - because I've been dealing with here-to...

...Snow Leopard do have show stopping issues; When creating a file we get this error: The Finder can?t complete the operation because some data in <FILENAME> can?t be read or written. (Error code -36) The file that should have appeared on the windows share is there but 0B in size, the mac "turd" ._ file is present, 4096B in size, and looks "good"? (apologies for the "turd" expression but macs do s**t all over the file system!) here is a dump of the ls for the directory (sensitive stuff removed): debian01:/mnt/remotedata/Jobs/Current/79700 NOSS Reports/Original# ls...

On 5/17/2011 2:58 AM, Eric Christopher wrote: > On May 14, 2011, at 3:08 AM, Eric Niebler wrote: > >> Just a heads up that the llvm build appears to be broken on cygwin. I >> haven't investigated, but here's the failures: >> >> llvm[3]: Compiling X86ISelDAGToDAG.cpp for Release+Asserts build >>

...e platforms (on powerpc there's at least 3 or 4 that have qemu emulation and support some form of PCI) don't have an existing way to convey the information that a device bypasses the IOMMU (if any). ? - Even if we add such a mechanism (new property in the device-tree), we end up with a big turd: Because we need to be compatible with older qemus, we essentially need a quirk that will make all virtio devices assume that property is present. That will of course break whenever we try to use another implementation of virtio on powerpc which doesn't bypass the iommu. We don't have a wa...

On 07/29/2015 07:40 PM, Chris Murphy wrote: > On Wed, Jul 29, 2015 at 4:37 PM, Warren Young <wyml at etr-usa.com> wrote: > >> Security is *always* opposed to convenience. > False. OS X by default runs only signed binaries, and if they come > from the App Store they run in a sandbox. User gains significant > security with this, and are completely unaware of it. There is

...e platforms (on powerpc there's at least 3 or 4 that have qemu emulation and support some form of PCI) don't have an existing way to convey the information that a device bypasses the IOMMU (if any). ? - Even if we add such a mechanism (new property in the device-tree), we end up with a big turd: Because we need to be compatible with older qemus, we essentially need a quirk that will make all virtio devices assume that property is present. That will of course break whenever we try to use another implementation of virtio on powerpc which doesn't bypass the iommu. We don't have a wa...

On Tue, 2018-08-07 at 23:31 -0700, Christoph Hellwig wrote: > > You don't need to set them the time you go secure. You just need to > set the flag from the beginning on any VM you might want to go secure. > Or for simplicity just any VM - if the DT/ACPI tables exposed by > qemu are good enough that will always exclude a iommu and not set a > DMA offset, so nothing will

On Tue, 2018-08-07 at 23:31 -0700, Christoph Hellwig wrote: > > You don't need to set them the time you go secure. You just need to > set the flag from the beginning on any VM you might want to go secure. > Or for simplicity just any VM - if the DT/ACPI tables exposed by > qemu are good enough that will always exclude a iommu and not set a > DMA offset, so nothing will

...there's at least 3 or 4 that have qemu > emulation and support some form of PCI) don't have an existing way to > convey the information that a device bypasses the IOMMU (if any). > > - Even if we add such a mechanism (new property in the device-tree), > we end up with a big turd: Because we need to be compatible with older > qemus, we essentially need a quirk that will make all virtio devices > assume that property is present. That will of course break whenever we > try to use another implementation of virtio on powerpc which doesn't > bypass the iommu. &gt...

Hi, Just a question, For you, what is the more reliable kernel for an asterisk prod server... Thanks

Hi T. Turtle, Did you ever get a response from this? Old Geek Son OGS ----- Original Message ----- From: Turd Turtle To: fxruby-users at rubyforge.org Sent: Saturday, August 29, 2009 6:30 PM Subject: [fxruby-users] How to install the RI doc into FXRI ? Hi, Man, this is ironic. When I typed "gem update" or something like that, so that all my gems updated, my FXRI no longer loads the...