AIX 6.1, POWER5 and Spectre/Meltdown Post: 303010868

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my...

2. AIX

Problem with knlist in AIX 5.3 for Power5 processor

Hi all, I have a AIX 5.3 Installation on the Power5 processor. I am using the knlist API for getting the details of the CPU details like user cpu, kernel cpu, idle cpu and wait cpu. My code is working fine on other Installations of AIX like PowerPC_POWER4 but it is giving wrong values on Power5...

3. AIX

Upgrading Power5 from 5.3 to...

I have a power5 that I would like to update and bring everything forward. I am wondering about trouble-free upgrades. Is it better to go 5.3 -> 7 or 5.3 ->6 ->7? The power5 box is behind and hopefully can learn from experiences here. Thanks.

4. AIX

POWER5+ 2.1Gz cpu wattage ?

Hello, What is wattage of POWER5+ 2.1Gz CPU ? It's dual-core 90nm chip. At least approximately ? thanks, Vilius

5. AIX

Power5 9111-520 reload of AIX 6.1 - help needed

Hello all, I am hoping someone can point me in the right direction here. We had a machine running AIX 6.1 that someone completely corrupted, so we decided to re-load it from media. I was able to boot into DVD media, select options for complete (destructive) install, AIX standard, etc. The...

6. War Stories

Linus Torvalds reply about Meltdown and Spectre.

Apologies if this is the wrong forum but... ...This is hard hitting stuff. LKML: Linus Torvalds: Re: x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

7. What is on Your Mind?

Meltdown and Spectre CPU bugs

This seems a bit serious: Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs � The Register Vulnerability Note VU#584653 - CPU hardware vulnerable to side-channel attacks Project Zero: Reading privileged memory with a side-channel

LEARN ABOUT DEBIAN

stg-sink

STG-SINK(1)							   StGit Manual 						       STG-SINK(1)

NAME

       stg-sink - Send patches deeper down the stack

SYNOPSIS

       stg sink [-t <target patch>] [-n] [<patches>]

DESCRIPTION

       This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
       patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
       more easily committed or pushed.

       If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
       option allows to place them under any applied patch.

       Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
       (unless --nopush is also given) pushing back into place the formerly-applied patches.

OPTIONS

       -n, --nopush
	   Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.

       -t TARGET, --to TARGET
	   Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.

       -k, --keep
	   Keep the local changes.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							       STG-SINK(1)